Triple
T5250524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Devonshire |
E118574
|
entity |
| Predicate | firstCreationYear |
P61740
|
FINISHED |
| Object | 1694 |
—
|
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: 1694 | Statement: [Duke of Devonshire, firstCreationYear, 1694]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCreationYear Context triple: [Duke of Devonshire, firstCreationYear, 1694]
-
A.
firstRunningYear
Indicates the year in which something (such as an event, service, or operation) first began running or was initially active.
-
B.
firstVersionYear
Indicates the calendar year in which the first version or initial release of something was created, published, or made available.
-
C.
firstProductionYear
Indicates the year in which something (such as a product, work, or item) was first produced.
-
D.
firstInscriptionYear
Indicates the year in which an entity was first inscribed, recorded, or officially entered into a relevant register or list.
-
E.
firstSerializationYear
Indicates the year in which an entity (such as a work or series) was first serialized or began its initial serialized publication.
- 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b79ae0c81908a9b8614f6886259 |
completed | March 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69bd77c30bac8190a883ca45da35d667 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd787975788190848ffbac87896efe |
completed | March 20, 2026, 4:40 p.m. |
Created at: March 20, 2026, 1:50 p.m.