Triple
T14726621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chippenham (UK Parliament constituency) |
E345960
|
entity |
| Predicate | recreatedInYear |
P16356
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Chippenham (UK Parliament constituency), recreatedInYear, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recreatedInYear Context triple: [Chippenham (UK Parliament constituency), recreatedInYear, 2010]
-
A.
reconstructionYear
Indicates the year in which something was rebuilt, restored, or reconstructed after damage, alteration, or destruction.
-
B.
recreated
chosen
Indicates that an entity has been created again or restored, typically after being removed, destroyed, or significantly altered.
-
C.
revivalYear
Indicates the year in which something (such as a work, practice, or institution) was brought back into active use or renewed after a period of decline or inactivity.
-
D.
reintroducedInYear
Indicates that an entity, previously absent or discontinued, was brought back or reinstated in a specified year.
-
E.
rediscoveryYear
Indicates the year in which something that was previously known but lost, forgotten, or overlooked was found or recognized again.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec26013c8819090512f8b4df9cc87 |
completed | April 14, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69de657e174481909da0437556334a04 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.