Triple
T17441661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Devon |
E424668
|
entity |
| Predicate | MPHasRepresentedSince |
P8979
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Central Devon, MPHasRepresentedSince, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MPHasRepresentedSince Context triple: [Central Devon, MPHasRepresentedSince, 2010]
-
A.
representedInCongressSince
Indicates that an entity has served as a representative in a legislative congress continuously since a specified date or time.
-
B.
representedByPartySince
Indicates that an entity has been represented by a particular party starting from a specified point in time.
-
C.
hasHistoricalPartyRepresentation
Indicates that an entity has been represented or affiliated with a particular political party at some point in its history.
-
D.
hasRepresented
Indicates that one entity has acted or served as an official representative or agent for another entity.
-
E.
representedInCongressBy
chosen
Indicates that one entity serves as the official congressional representative (e.g., legislator) for another entity (such as a person, group, or geographic area).
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44ff82bbc819095dd0621137da809 |
completed | April 19, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69e3b030eac481909b8402719cc3102e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.