Triple
T24110708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huynh Van Ngo |
E597361
|
entity |
| Predicate | opponentInBattleOfApBac |
P18835
|
FINISHED |
| Object | Viet Cong |
—
|
NE NERFINISHED |
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: Viet Cong | Statement: [Huynh Van Ngo, opponentInBattleOfApBac, Viet Cong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentInBattleOfApBac Context triple: [Huynh Van Ngo, opponentInBattleOfApBac, Viet Cong]
-
A.
battleOpponent
chosen
Indicates that two entities are engaged in or designated as opponents in a battle or combat scenario.
-
B.
wasOpponentOf
Indicates that one entity competed or conflicted against another as an adversary in some contest, game, or confrontation.
-
C.
facedOpponent
Indicates that one entity directly confronted or competed against another as an opponent in a contest, conflict, or challenge.
-
D.
opponentInBattleOfRaphia
Indicates that two entities were opposing sides against each other in the historical Battle of Raphia.
-
E.
opponentInBattleOfIaDrang
Indicates that one entity served as an opposing force to another in the Battle of Ia Drang.
- 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_69e288c60f9c8190af948d7354aedbeb |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1de1ae5b08190a33b7fbaaad10191 |
completed | April 29, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:03 p.m.