Triple
T3229504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Paterson |
E67703
|
entity |
| Predicate | assumedOfficeAsGovernorBy |
P14741
|
FINISHED |
| Object | line of succession |
—
|
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: line of succession | Statement: [David Paterson, assumedOfficeAsGovernorBy, line of succession]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assumedOfficeAsGovernorBy Context triple: [David Paterson, assumedOfficeAsGovernorBy, line of succession]
-
A.
officeHeldAsGovernor
Indicates that an entity holds or has held the official position of governor of a political or administrative region.
-
B.
servedAsGovernorUntil
Indicates that an entity held the position of governor up to a specified end date or time.
-
C.
officeAssumedAsLieutenantGovernor
chosen
Indicates that an individual has formally taken on and begun serving in the role of lieutenant governor.
-
D.
hadGovernor
Indicates that an administrative region or political entity was governed by a specific person who held the office of governor.
-
E.
governorBasedIn
Indicates that a governor carries out their official duties or has their primary office located in a specified place.
- 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_69ad858c61888190a31196310d9b30b5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaeb826588190a93bcfb1242310e7 |
completed | March 8, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0dc2248190a38c40f4e06cd41c |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:08 p.m.