Triple
T36346523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford family |
E895079
|
entity |
| Predicate | successorPatriarch |
P147441
|
FINISHED |
| Object | Edsel Ford |
—
|
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: Edsel Ford | Statement: [Ford family, successorPatriarch, Edsel Ford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorPatriarch Context triple: [Ford family, successorPatriarch, Edsel Ford]
-
A.
successorAsPatriarch
chosen
Indicates that one entity becomes the next patriarch, directly succeeding another in that patriarchal role.
-
B.
successorAsSupreme
Indicates that one entity becomes the next holder of the position or role of supreme authority after another entity.
-
C.
successorAsBishopOfConstantinople
Indicates that one individual became the next bishop of Constantinople following another individual in that ecclesiastical office.
-
D.
successorRuler
Indicates that one ruler directly follows another in holding a position of authority or rule.
-
E.
successorInNorthernLands
Indicates that one entity becomes the next holder of a role, title, or position specifically within the context of the Northern Lands.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a006ef900148190ba52daf566882a03 |
completed | May 10, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_6a006c76ae748190bfe466d7d17d321e |
completed | May 10, 2026, 11:31 a.m. |
Created at: May 3, 2026, 4:09 p.m.