Triple
T2870399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huntingdonshire |
E63545
|
entity |
| Predicate | re-establishedAsDistrict |
P9113
|
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: [Huntingdonshire, re-establishedAsDistrict, 1974]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: re-establishedAsDistrict Context triple: [Huntingdonshire, re-establishedAsDistrict, 1974]
-
A.
redistrictedBy
Indicates that an entity’s boundaries or districts have been altered or redefined by another specified agent or authority.
-
B.
formerDistrict
Indicates that one entity previously served as a district of another entity but no longer holds that status.
-
C.
redistrictedIn
Indicates that the boundaries or jurisdiction of an area have been changed or reassigned within a specified district or administrative division.
-
D.
redistrictedAfter
Indicates that one districting arrangement or boundary configuration was created or implemented following, and typically as a result of, another districting arrangement.
-
E.
reestablishedInYear
chosen
Indicates that an entity, previously existing and then discontinued or dissolved, was brought back into existence or operation in the specified year.
- 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_69ab4c42fb8c8190b36e161d47c03b81 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfe2dcb48190a194253e733d14af |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.