Triple
T36121125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Trials of Henry Kissinger |
E1044742
|
entity |
| Predicate | examinesRoleInEvent |
P85529
|
FINISHED |
| Object | Vietnam War peace negotiations |
—
|
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: Vietnam War peace negotiations | Statement: [The Trials of Henry Kissinger, examinesRoleInEvent, Vietnam War peace negotiations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: examinesRoleInEvent Context triple: [The Trials of Henry Kissinger, examinesRoleInEvent, Vietnam War peace negotiations]
-
A.
eventRole
Indicates the specific function, capacity, or part an entity plays within an event or occurrence.
-
B.
relationshipToEvent
chosen
Indicates the specific way an entity is connected or related to a particular event.
-
C.
roleInCalendar
Indicates that an entity holds a specific role or function within the context of a particular calendar or scheduled event.
-
D.
attendanceRole
Indicates the specific capacity or role in which an entity participates in an attendance-related event or activity.
-
E.
eventParticipant
Indicates that an entity takes part in, is involved in, or participates in 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.