Triple
T9624785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doncaster North |
E232431
|
entity |
| Predicate | MPInOfficeSince |
P18957
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [Doncaster North, MPInOfficeSince, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MPInOfficeSince Context triple: [Doncaster North, MPInOfficeSince, 2005]
-
A.
timeInOfficeBeginsIn
chosen
Indicates the point in time or date when an entity’s term, tenure, or period in office starts.
-
B.
timeInOfficeCharacteristic
Indicates a characteristic or attribute specifically related to the duration or period an entity spends in office or in a particular official role.
-
C.
timeInOfficeRelation
Indicates a temporal relationship specifying the duration or period that an entity holds or held a particular office or position.
-
D.
occupiesSince
Indicates that an entity has continuously occupied or held a position, place, or role starting from a specified point in time.
-
E.
hasRelativeInOffice
Indicates that one entity has a family member who holds or held a particular office or official position.
- 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_69ca848793ec8190a93a12383a754dc0 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9ad76b148190a38fadee06594db4 |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5aa1d2c8190a287bf1cf4a3037e |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:10 p.m.