Triple
T642447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eisenhower administration |
E16767
|
entity |
| Predicate | inOfficeDuring |
P16852
|
FINISHED |
| Object | Korean War armistice |
—
|
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: Korean War armistice | Statement: [Eisenhower administration, inOfficeDuring, Korean War armistice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inOfficeDuring Context triple: [Eisenhower administration, inOfficeDuring, Korean War armistice]
-
A.
worksWithOffice
Indicates that an entity collaborates or is professionally associated with a particular office or office-based organization.
-
B.
officeStart
Indicates the time or date at which an entity’s term, role, or period of holding office begins.
-
C.
includedOffice
Indicates that one office is contained within, or forms part of, another office or organizational unit.
-
D.
usedByOffice
Indicates that something is utilized, operated, or employed by an office or office-related entity.
-
E.
orderInOffice
Indicates that one entity holds a specific sequential position or rank within a defined term or period of holding an office or official role.
- F. None of above. chosen
Provenance (4 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49f03db7481909e49c325c5f7cdae |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0a0ab481909871461418a00be7 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49dc0e6a08190b81d82a6f2571c41 |
completed | March 1, 2026, 8:12 p.m. |
Created at: March 1, 2026, 7:36 p.m.