Triple
T37267028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harry R. Haldeman |
E924412
|
entity |
| Predicate | startTimeStatement |
P66434
|
FINISHED |
| Object | Became White House Chief of Staff in 1969 |
—
|
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: Became White House Chief of Staff in 1969 | Statement: [Harry R. Haldeman, startTimeStatement, Became White House Chief of Staff in 1969]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeStatement Context triple: [Harry R. Haldeman, startTimeStatement, Became White House Chief of Staff in 1969]
-
A.
startTimeNote
Indicates the specific time-related note or annotation associated with when an event or action begins.
-
B.
endTimeStatement
Indicates the point in time at which a described event, action, or state is considered to have finished.
-
C.
startTimeDetail
Indicates the specific, often more granular or formatted, time at which an event or action begins.
-
D.
positionStartTime
chosen
Indicates the time at which a position, role, or placement begins.
-
E.
startTimeAsCardinal
Indicates the specific clock time at which an event or action begins, expressed as a cardinal (numeric) value rather than a textual or formatted time.
- 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00be8ee4bc8190b795d9606f0e490c |
completed | May 10, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_6a00bde163c88190867104bd08cac2ee |
completed | May 10, 2026, 5:18 p.m. |
Created at: May 3, 2026, 4:15 p.m.