Triple
T8805424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reckless: Henry Kissinger and the Tragedy of Vietnam |
E209516
|
entity |
| Predicate | placesEventIn |
P19113
|
FINISHED |
| Object | Cold War context |
—
|
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: Cold War context | Statement: [Reckless: Henry Kissinger and the Tragedy of Vietnam, placesEventIn, Cold War context]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placesEventIn Context triple: [Reckless: Henry Kissinger and the Tragedy of Vietnam, placesEventIn, Cold War context]
-
A.
eventIn
chosen
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
B.
eventLocationOfNotableActivity
Indicates that a location is the place where a notable or significant activity or event involving the related entity occurred.
-
C.
sealEventPlace
Indicates the place where a sealing event or act of sealing occurs.
-
D.
organisedEvent
Indicates that an entity planned, coordinated, and carried out an event.
-
E.
countryHostedEvent
Indicates that a specific country served as the host location for a particular event.
- 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_69ca836320e48190b5cf585b90a322c4 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fd04eb88190acc4e085d82016c0 |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:44 p.m.