Triple
T8920503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drayton |
E212401
|
entity |
| Predicate | changedAdministrativeCountyIn |
P62719
|
FINISHED |
| Object | 1974 |
—
|
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 | Statement: [Drayton, changedAdministrativeCountyIn, 1974]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changedAdministrativeCountyIn Context triple: [Drayton, changedAdministrativeCountyIn, 1974]
-
A.
historicalCountyChange
chosen
Indicates that a county’s administrative boundaries or status have been altered over time, such as through creation, dissolution, merger, or territorial reassignment.
-
B.
administrativeCenterMovedFrom
Indicates that the role of administrative center was previously located in one place and has been transferred or relocated from that original location to another.
-
C.
countySeatMovedTo
Indicates that the official county seat was relocated from one place to another.
-
D.
previousCounty
Indicates that one county was the immediately preceding county associated with an entity before the current or later county.
-
E.
movedPremises
Indicates that an entity has changed its location or base of operations from one set of premises to another.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc664f099c8190be6d20a4574212ca |
completed | April 1, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:56 p.m.