Triple
T11998668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rufus W. Peckham |
E285594
|
entity |
| Predicate | tookOfficeOn |
P18957
|
FINISHED |
| Object | 1896-01-06 |
—
|
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: 1896-01-06 | Statement: [Rufus W. Peckham, tookOfficeOn, 1896-01-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookOfficeOn Context triple: [Rufus W. Peckham, tookOfficeOn, 1896-01-06]
-
A.
termOfOfficeInaugurated
Indicates the event or date on which an individual officially begins their term of office through an inauguration.
-
B.
succeededToOfficeIn
Indicates that one entity assumed or took over an office or position previously held by another entity at a specified time or in a specified succession.
-
C.
inaugurationDate
Indicates the date on which an official ceremony formally installs a person into a specific office or position.
-
D.
inauguratedFor
Indicates that a formal ceremony or event was held to officially begin or dedicate something specifically for a particular entity, role, or purpose.
-
E.
timeInOfficeBeginsIn
chosen
Indicates the point in time or date when an entity’s term, tenure, or period in office starts.
- 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903c26d7881909b67a31d04882eb5 |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902b245cc8190af96a9c2bd9c6250 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.