Triple
T18706357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Eaton |
E457376
|
entity |
| Predicate | officeHeldWithStartTime |
P25646
|
FINISHED |
| Object | United States Secretary of War, 1829 |
—
|
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: United States Secretary of War, 1829 | Statement: [John Eaton, officeHeldWithStartTime, United States Secretary of War, 1829]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeHeldWithStartTime Context triple: [John Eaton, officeHeldWithStartTime, United States Secretary of War, 1829]
-
A.
officeHeldDuring
chosen
Indicates that a person occupied a specific official position during a particular time period.
-
B.
officeForStartEndTime
Indicates that an office is assigned or valid for a specific time interval defined by a start time and an end time.
-
C.
officeHeldInPeriod
Indicates that an entity held a particular office or position during a specified time period.
-
D.
officeHeldOf
Indicates that a specific office or position is (or was) held by a particular person or entity.
-
E.
officeHeldIn
Indicates that a particular office or position is held within or associated with a specific geographic or administrative location.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5671717b88190974f542015f641e8 |
completed | April 19, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:50 a.m.