Triple
T20751371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gentry |
E510726
|
entity |
| Predicate | hasVariantForm |
P457
|
FINISHED |
| Object |
Gentry (surname)
Gentry is an English-language surname historically associated with the social class of landowning gentry and their descendants.
|
E1448347
|
NE FINISHED |
How this triple was built (4 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Gentry (surname) | Statement: [Gentry, hasVariantForm, Gentry (surname)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gentry (surname) Context triple: [Gentry, hasVariantForm, Gentry (surname)]
-
A.
Gentry
Gentry is a given name most notably borne by American science fiction writer and engineer Gentry Lee.
-
B.
Brent (surname)
Brent is an English surname of Old English and Celtic origin, commonly derived from place names associated with hills, high ground, or the River Brent.
-
C.
Hamilton (surname)
Hamilton is a common Scottish and English surname of Norman origin, borne by numerous notable figures in politics, science, and the arts.
-
D.
Douglas (surname)
Douglas (surname) is a Scottish family name of Gaelic origin historically associated with a powerful Lowland clan and widely borne in English-speaking countries.
-
E.
Gerrity
Gerrity is a surname, likely of Irish origin, that serves as a spelling variant of the name Gerry.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Gentry (surname) Triple: [Gentry, hasVariantForm, Gentry (surname)]
Generated description
Gentry is an English-language surname historically associated with the social class of landowning gentry and their descendants.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Gentry (surname) Target entity description: Gentry is an English-language surname historically associated with the social class of landowning gentry and their descendants.
-
A.
Gentry
Gentry is a given name most notably borne by American science fiction writer and engineer Gentry Lee.
-
B.
Brent (surname)
Brent is an English surname of Old English and Celtic origin, commonly derived from place names associated with hills, high ground, or the River Brent.
-
C.
Hamilton (surname)
Hamilton is a common Scottish and English surname of Norman origin, borne by numerous notable figures in politics, science, and the arts.
-
D.
Douglas (surname)
Douglas (surname) is a Scottish family name of Gaelic origin historically associated with a powerful Lowland clan and widely borne in English-speaking countries.
-
E.
Gerrity
Gerrity is a surname, likely of Irish origin, that serves as a spelling variant of the name Gerry.
- F. None of above. chosen
Provenance (5 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c22ad0c8819087a8db2bac8dd408 |
completed | April 21, 2026, 12:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a08e8467a0c819096982615570c725a |
completed | May 16, 2026, 9:57 p.m. |
| NEDg | Description generation | batch_6a08e91f9e648190a39d1ff3dc3ca040 |
completed | May 16, 2026, 10:01 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a08e9d349e88190b3fb6b30744df6c5 |
completed | May 16, 2026, 10:04 p.m. |
Created at: April 16, 2026, 12:34 p.m.