Triple
T24110706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huynh Van Ngo |
E597361
|
entity |
| Predicate | roleAtBattleOfApBac |
P28183
|
FINISHED |
| Object | South Vietnamese commander |
—
|
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: South Vietnamese commander | Statement: [Huynh Van Ngo, roleAtBattleOfApBac, South Vietnamese commander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtBattleOfApBac Context triple: [Huynh Van Ngo, roleAtBattleOfApBac, South Vietnamese commander]
-
A.
notableBattleRole
chosen
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
B.
roleInBattleOfMabila
Indicates the specific function, position, or participation an entity had in the Battle of Mabila.
-
C.
foughtAs
Indicates that an entity participated in a conflict or war in the capacity, role, or identity specified by another entity.
-
D.
refersToPersonNotableBattle
Indicates that a person is associated with or identified by a specific notable battle in which they played a significant role.
-
E.
roleAtBattleOfToulon
Indicates the specific role, position, or function an entity held during the Battle of Toulon.
- 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.