Triple
T19311855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laos and Vietnam |
E482990
|
entity |
| Predicate | shareHistoricalConflictAndCooperation |
P55438
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Laos and Vietnam, shareHistoricalConflictAndCooperation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareHistoricalConflictAndCooperation Context triple: [Laos and Vietnam, shareHistoricalConflictAndCooperation, yes]
-
A.
hasHistoricalPeriodOfConflict
Indicates that there exists a specific historical period during which the related entities were engaged in conflict or hostilities.
-
B.
opponentInHistoricalConflict
Indicates that two entities stood on opposing sides in a specific historical conflict or war.
-
C.
conflictOrCooperationWith
chosen
Indicates the presence, nature, or degree of either conflict or cooperation between two entities.
-
D.
conflictHistory
Indicates a history of conflict or antagonistic interactions that have occurred between the related entities.
-
E.
partOfHistoricalConflict
Indicates that one entity participated in, belonged to, or was involved as a component of a larger historical conflict or 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e604ce5de081909811c49f56ba94bb |
completed | April 20, 2026, 10:49 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:32 p.m.