Triple
T37497805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dora Bland |
E931875
|
entity |
| Predicate | childrenCountWithWilliamDukeOfClarence |
P188402
|
FINISHED |
| Object | 10 |
—
|
LITERAL FINISHED |
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: 10 | Statement: [Dora Bland, childrenCountWithWilliamDukeOfClarence, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: childrenCountWithWilliamDukeOfClarence Context triple: [Dora Bland, childrenCountWithWilliamDukeOfClarence, 10]
-
A.
createdDukeOfClarence
Indicates the relationship in which one entity formally granted or established the noble title "Duke of Clarence" for another entity.
-
B.
createdDukeOfRichmondBy
Indicates the act by which an authority formally established or conferred the title of Duke of Richmond upon a person.
-
C.
heirAfterWilliamAdelin
Indicates that one entity became the designated heir after the death of William Adelin.
-
D.
createdDukeOfYorkBy
Indicates the action by which an authority or agent formally conferred or established the title of Duke of York upon a person.
-
E.
currentDukeOfCornwall
Indicates that one entity holds the present title or role of Duke of Cornwall in relation to another entity.
- F. None of above. chosen
Provenance (4 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_69f76ec457a4819094eeb3aed9baac11 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba67f78348190ab160988e4698394 |
completed | May 6, 2026, 8:37 p.m. |
Created at: May 3, 2026, 4:17 p.m.