Triple
T5979015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Demilitarized Zone (Vietnam) |
E133072
|
entity |
| Predicate | statusDuringVietnamWar |
P19322
|
FINISHED |
| Object | buffer zone |
—
|
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: buffer zone | Statement: [Demilitarized Zone (Vietnam), statusDuringVietnamWar, buffer zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusDuringVietnamWar Context triple: [Demilitarized Zone (Vietnam), statusDuringVietnamWar, buffer zone]
-
A.
positionOnVietnamWar
Indicates a person or entity’s stance, opinion, or policy position regarding the Vietnam War.
-
B.
statusDuringWar
chosen
Indicates the role, condition, or classification an entity held specifically during a period of war.
-
C.
statusDuringColdWar
Indicates the political or diplomatic status or alignment that an entity held specifically during the Cold War period.
-
D.
estimatedNorthVietnameseCasualties
Indicates the reported or calculated number of casualties attributed to North Vietnamese forces in a given context or event.
-
E.
statusBeforeWar
Indicates the condition or situation of an entity as it existed prior to the onset of a specified war.
- 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_69c0086f45e8819098f73dd16d45ec9d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04dc2243c8190bd3488e7b24af985 |
completed | March 22, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c049dcb3c081908ccc9b4d4b210229 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:04 p.m.