Triple
T9318141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cu Chi District |
E224173
|
entity |
| Predicate | warLegacy |
P88059
|
FINISHED |
| Object | remnants of military installations |
—
|
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: remnants of military installations | Statement: [Cu Chi District, warLegacy, remnants of military installations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warLegacy Context triple: [Cu Chi District, warLegacy, remnants of military installations]
-
A.
warCustom
Indicates a relationship in which one party engages in or applies a particular war-related practice, norm, or customary way of conducting warfare toward or involving another.
-
B.
battleStarsWorldWarII
Indicates that the entity has received battle stars for participation in World War II military operations.
-
C.
warFrontDepicted
Indicates that a particular war front or battlefield area is visually represented or shown in a depiction.
-
D.
warAim
Indicates the strategic objective or intended outcome that a party seeks to achieve through engaging in war or armed conflict.
-
E.
warPeriod
Indicates a time span during which a state of war or armed conflict is ongoing between parties.
- 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_69ca8426d48481909596360f7791c7dd |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd358b66148190a918c107490c8406 |
completed | April 1, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc955a38108190b602d1e73725f11b |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:38 p.m.