Triple
T12507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gavin Newsom |
E252
|
entity |
| Predicate | positionEnd |
P140
|
FINISHED |
| Object | Lieutenant Governor of California:2019-01-07 |
—
|
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: Lieutenant Governor of California:2019-01-07 | Statement: [Gavin Newsom, positionEnd, Lieutenant Governor of California:2019-01-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionEnd Context triple: [Gavin Newsom, positionEnd, Lieutenant Governor of California:2019-01-07]
-
A.
positionHeld
Indicates that an entity occupies or has occupied a specific role, job, office, or position within an organization or context.
-
B.
endPoint
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
-
C.
startPoint
Indicates the initial location or position from which an object, path, or action begins.
-
D.
endDate
chosen
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
E.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
- 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_69a23d7ad88c8190bffe8ab091d86642 |
completed | Feb. 28, 2026, 12:57 a.m. |
| NER | Named-entity recognition | batch_69a243abb2ec8190937365e5ecec52ad |
completed | Feb. 28, 2026, 1:23 a.m. |
| PD | Predicate disambiguation | batch_69a23fe9470c8190918a6ca1df168646 |
completed | Feb. 28, 2026, 1:07 a.m. |
Created at: Feb. 28, 2026, 1:02 a.m.