Triple
T707273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Cornwall |
E14127
|
entity |
| Predicate | previousHolderStartDate |
P19035
|
FINISHED |
| Object | 1952-02-06 |
—
|
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: 1952-02-06 | Statement: [Duke of Cornwall, previousHolderStartDate, 1952-02-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousHolderStartDate Context triple: [Duke of Cornwall, previousHolderStartDate, 1952-02-06]
-
A.
lastHolder
Indicates that the subject is the most recent entity to have possessed, owned, or held the object.
-
B.
currentHolderStart
Indicates the point in time when an entity’s current holder or possessor first began holding it.
-
C.
officeHolderStartTime
Indicates the date and time at which an individual begins holding a particular office or position.
-
D.
originalHolder
Indicates that an entity is the initial possessor or owner of another entity before any transfer, change, or reassignment occurs.
-
E.
hasPreviousHolder
Indicates that an entity was formerly held, occupied, or possessed by another specified entity before the current one.
- 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_69a493494ec48190ae6751683625a9ba |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a5c011948190b2cfccd8fe722742 |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f0217081908268b3f47e72f8df |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a5bed20c81909ecc28bf42594e72 |
completed | March 1, 2026, 8:46 p.m. |
Created at: March 1, 2026, 7:36 p.m.