Triple
T22676634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gio Linh district |
E560361
|
entity |
| Predicate | hasPostWarIssues |
P149202
|
FINISHED |
| Object | unexploded ordnance |
—
|
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: unexploded ordnance | Statement: [Gio Linh district, hasPostWarIssues, unexploded ordnance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostWarIssues Context triple: [Gio Linh district, hasPostWarIssues, unexploded ordnance]
-
A.
postwarOutcome
Indicates the result or consequences that follow for a party or situation after a war has ended.
-
B.
postWarFunction
Indicates how something operated, was used, or what role it served in the period following a war.
-
C.
usedAfterWar
Indicates that an entity came into use only after a specific war or conflict had ended.
-
D.
postWarOrder
Indicates the arrangement of political, economic, and social relations established among actors after a war has ended.
-
E.
legalStatusAfterWar
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
- 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1785ca1e08190af1a6cdb51ca4fce |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:11 p.m.