Triple
T34173333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roger Griswold |
E876599
|
entity |
| Predicate | servedAsGovernorStart |
P25420
|
FINISHED |
| Object | 1811 |
—
|
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: 1811 | Statement: [Roger Griswold, servedAsGovernorStart, 1811]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsGovernorStart Context triple: [Roger Griswold, servedAsGovernorStart, 1811]
-
A.
servedAsGovernorNumber
Indicates the ordinal position in which an individual served as governor (e.g., first, second, third).
-
B.
servedAsGovernorUntil
Indicates that an entity held the position of governor up to a specified end date or time.
-
C.
officeHeldAsGovernor
Indicates that an entity holds or has held the official position of governor of a political or administrative region.
-
D.
succeededInOfficeAsGovernorBy
Indicates that one individual’s term as governor ended and was directly followed by another individual’s term in the same office.
-
E.
termStartAsGovernor
chosen
Indicates the date or point in time when an individual begins their term serving in the role of governor.
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff8aff48988190a48a440de8238ef9 |
completed | May 9, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69ff8a780404819082f48ceb21e7fe11 |
completed | May 9, 2026, 7:26 p.m. |
Created at: May 1, 2026, 1:54 a.m.