Triple
T39699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leader of the Opposition (UK) |
E785
|
entity |
| Predicate | currentHolderAssumedOffice |
P1814
|
FINISHED |
| Object | April 4, 2020 |
—
|
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: April 4, 2020 | Statement: [Leader of the Opposition (UK), currentHolderAssumedOffice, April 4, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentHolderAssumedOffice Context triple: [Leader of the Opposition (UK), currentHolderAssumedOffice, April 4, 2020]
-
A.
officeHolderOf
Indicates that a person holds or has held an official position or role within a specified organization, institution, or office.
-
B.
electedOffice
Indicates that an entity holds or has held a particular office or position as a result of an election.
-
C.
officeHolderStartTime
chosen
Indicates the date and time at which an individual begins holding a particular office or position.
-
D.
firstInOfficeTo
Indicates that one entity was the earliest or first to hold a particular office or position in relation to another entity or context.
-
E.
positionHeld
Indicates that an entity occupies or has occupied a specific role, job, office, or position within an organization or context.
- 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_69a247a8f6c08190bac804906d62ed5a |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24b80f4a8819090d2bffe29824b90 |
completed | Feb. 28, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69a24ab74c548190a54872e15c8394c3 |
completed | Feb. 28, 2026, 1:53 a.m. |
Created at: Feb. 28, 2026, 1:46 a.m.