Triple
T7041759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Edinburgh Council |
E163528
|
entity |
| Predicate | lastMajorReorganisation |
P44327
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [City of Edinburgh Council, lastMajorReorganisation, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastMajorReorganisation Context triple: [City of Edinburgh Council, lastMajorReorganisation, 1996]
-
A.
lastReform
Indicates the most recent reform or change that was applied to an entity, typically linking the entity to its latest reform event or version.
-
B.
furtherReorganizedOn
Indicates that an entity was reorganized again or to a greater extent on a specified later date or occasion.
-
C.
introducedReorganisationOn
Indicates that an entity initiated or implemented a reorganisation at or on a specific time, date, or occasion.
-
D.
partiallyReorganizedOn
Indicates that an entity has undergone some, but not complete, reorganization on or by another entity or process.
-
E.
reorganizationYear
chosen
Indicates the year in which an entity underwent a structural or organizational reorganization.
- 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_69c6885e7c1c8190be32a8f79ab4e0cf |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bb602081908bfa6186a1f5a4b4 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:36 p.m.