Triple
T3850784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Kingdom general election, 1970 |
E85289
|
entity |
| Predicate | forOffice |
P3103
|
FINISHED |
| Object | Member of Parliament |
—
|
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: Member of Parliament | Statement: [United Kingdom general election, 1970, forOffice, Member of Parliament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forOffice Context triple: [United Kingdom general election, 1970, forOffice, Member of Parliament]
-
A.
office
chosen
Indicates that an entity holds or occupies an official position, role, or post within an organization or institution.
-
B.
inOfficeFrom
Indicates that an entity holds a particular office or position starting from a specified date or time.
-
C.
otherOffice
Indicates that one office is an alternative or additional office associated with the same organization, person, or entity as another office.
-
D.
worksWithOffice
Indicates that an entity collaborates or is professionally associated with a particular office or office-based organization.
-
E.
officeFormation
Indicates the event or process by which an office or official position is created, established, or formally constituted.
- 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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeebcf67788190975105131baabc4b |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee750377c8190af70c79768c0edd8 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.