Triple
T5967186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Stanley, 1st Earl of Derby |
E132780
|
entity |
| Predicate | creationOfEarldomDate |
P31263
|
FINISHED |
| Object | 1485 |
—
|
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: 1485 | Statement: [Thomas Stanley, 1st Earl of Derby, creationOfEarldomDate, 1485]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creationOfEarldomDate Context triple: [Thomas Stanley, 1st Earl of Derby, creationOfEarldomDate, 1485]
-
A.
reignAsEarlOfHuntingdonStart
Indicates the time or event at which a person begins their tenure or rule as the Earl of Huntingdon.
-
B.
nobleTitleCreationDate
chosen
Indicates the date on which a particular noble title was formally created or granted.
-
C.
dateOfKnighthood
Indicates the specific date on which an individual was formally granted knighthood.
-
D.
reignAsEarlOfNorthumbriaStart
Indicates the time at which a person begins their tenure ruling in the position of Earl of Northumbria.
-
E.
successorAsEarlOfHuntingdon
Indicates that one person became the next Earl of Huntingdon following another person in that title or office.
- 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_69c0086deab081908550159ca23eec9b |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03fb7f8a88190a8bd45208bda4a03 |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0335a635881909c58c1ef0f97f1e8 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:03 p.m.