Triple
T20604961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buckinghamshire |
E506279
|
entity |
| Predicate | statusAfter1974 |
P140735
|
FINISHED |
| Object | retained as administrative county with 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: retained as administrative county with boundary changes | Statement: [Buckinghamshire, statusAfter1974, retained as administrative county with boundary changes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfter1974 Context triple: [Buckinghamshire, statusAfter1974, retained as administrative county with boundary changes]
-
A.
statusAfter1994
Indicates the status or condition of an entity specifically in the period after the year 1994.
-
B.
statusAfter1979
Indicates the status or condition of an entity specifically in the period following the year 1979.
-
C.
statusAfter1954
Indicates the status or condition that an entity has at some point after the year 1954.
-
D.
statusAfter1975
Indicates the status or condition that an entity has starting from the year 1975 onward.
-
E.
statusAfter1973
Indicates the status or condition of an entity as it exists at some point after the year 1973.
- 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa233e1881908749d2f29c2946e4 |
completed | April 20, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:41 a.m.