Triple
T36718508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Took family |
E906980
|
entity |
| Predicate | headOfFamilyOftenHeldOffice |
P126256
|
FINISHED |
| Object | Thain |
—
|
NE NERFINISHED |
How this triple was built (2 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: Thain | Statement: [Took family, headOfFamilyOftenHeldOffice, Thain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headOfFamilyOftenHeldOffice Context triple: [Took family, headOfFamilyOftenHeldOffice, Thain]
-
A.
headOfHouseSince
Indicates the time point or date from which an entity has held the role or position of head of a particular household.
-
B.
headOfOffice
Indicates that one entity serves as the chief or leading authority in charge of a particular office or organizational unit.
-
C.
headOfHouseOf
Indicates that one entity serves as the leader or principal authority of a particular household, family, or house.
-
D.
isHeadOf
Indicates that one entity holds the leading or principal authority position over another entity, such as an organization, group, or department.
-
E.
officeHolderParent
chosen
Indicates that one entity is the parent of another entity who holds or has held a particular office or official position.
- F. None of above.
Provenance (3 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:12 p.m.