Triple
T10073777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North East Cambridgeshire |
E213695
|
entity |
| Predicate | MPFirstElected |
P15306
|
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: [North East Cambridgeshire, MPFirstElected, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MPFirstElected Context triple: [North East Cambridgeshire, MPFirstElected, 2010]
-
A.
firstInOfficeTo
Indicates that one entity was the earliest or first to hold a particular office or position in relation to another entity or context.
-
B.
firstElectedToSenate
Indicates the event or relationship in which a person is initially chosen or wins election to serve as a member of a senate.
-
C.
endTimeMemberOfCongressFirstTerm
Indicates the date and time when an individual’s first term as a member of Congress concludes.
-
D.
firstElectionYear
chosen
Indicates the calendar year in which an entity (such as a person, office, or political body) first participated in or was subject to an election.
-
E.
firstElectionDate
Indicates the date on which an entity (such as a person or office) participated in or held its first election.
- 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_69ca839add308190b57d53b4ec21f2d0 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd015ad488190aee3a2bfb58fb855 |
completed | April 2, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69cd4b97870481908f7a89df10d58a9e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:59 p.m.