Triple
T3036521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agreement on the Cessation of Hostilities in Vietnam |
E83022
|
entity |
| Predicate | electionsScheduledFor |
P45149
|
FINISHED |
| Object | 1956 |
—
|
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: 1956 | Statement: [Agreement on the Cessation of Hostilities in Vietnam, electionsScheduledFor, 1956]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electionsScheduledFor Context triple: [Agreement on the Cessation of Hostilities in Vietnam, electionsScheduledFor, 1956]
-
A.
hasElectionsFor
Indicates that a governing body, jurisdiction, or organization conducts elections to select or appoint members to a specified office, role, or representative body.
-
B.
electionHeldIn
Indicates that an election event took place within a specific geographic or political location.
-
C.
electionDate
Indicates the specific calendar date on which an election is scheduled to be or was held.
-
D.
nextElection
Indicates the upcoming scheduled election associated with a given political body, office, or jurisdiction.
-
E.
houseElectionsHeld
Indicates that elections have been conducted to choose members of a legislative house or lower chamber.
- 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_69ad8b2298908190a7cb4e9bdbf064d0 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9b2cd4988190b52fe3616ecbe9ef |
completed | March 8, 2026, 3:52 p.m. |
| PD | Predicate disambiguation | batch_69ad961e2a408190afb1759132701305 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97ba55dc8190b6dddddfb751cf64 |
completed | March 8, 2026, 3:37 p.m. |
Created at: March 8, 2026, 3:01 p.m.