Triple
T27432805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enfield Southgate |
E690691
|
entity |
| Predicate | recreatedOrModified |
P16356
|
FINISHED |
| Object | 1974 boundary changes |
—
|
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: 1974 boundary changes | Statement: [Enfield Southgate, recreatedOrModified, 1974 boundary changes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recreatedOrModified Context triple: [Enfield Southgate, recreatedOrModified, 1974 boundary changes]
-
A.
recreated
chosen
Indicates that an entity has been created again or restored, typically after being removed, destroyed, or significantly altered.
-
B.
recreatedFor
Indicates that one entity has been created again or reproduced specifically for the benefit, use, or purpose of another entity.
-
C.
reworkedBy
Indicates that an existing work, product, or result has been modified, revised, or substantially altered by a particular agent.
-
D.
rebuiltOrModifiedDuring
Indicates that an existing entity was reconstructed, renovated, or otherwise significantly altered during a specified time period or event.
-
E.
wasReconstructed
Indicates that something previously existing was rebuilt or restored after damage, destruction, or alteration.
- 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_69ef52003fb48190b0f1295246182a86 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 12:42 p.m.