Triple
T6774617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 66th Regiment, People's Army of Vietnam |
E155124
|
entity |
| Predicate | roleInBattleOfIaDrang |
P28183
|
FINISHED |
| Object | major combat role |
—
|
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: major combat role | Statement: [66th Regiment, People's Army of Vietnam, roleInBattleOfIaDrang, major combat role]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBattleOfIaDrang Context triple: [66th Regiment, People's Army of Vietnam, roleInBattleOfIaDrang, major combat role]
-
A.
positionOnVietnamWar
Indicates a person or entity’s stance, opinion, or policy position regarding the Vietnam War.
-
B.
roleInKoreanWar
Indicates the specific function, position, or involvement an entity had during the Korean War.
-
C.
notableBattleRole
chosen
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
D.
roleAtBattleOfChancellorsville
Indicates the specific role, position, or function an entity held during the Battle of Chancellorsville.
-
E.
roleInMexicanAmericanWar
Indicates that an entity participated in the Mexican–American War in a specified capacity or function.
- 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_69c68812ef7c819099369f51febb725c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d24ddaf08190baffbff991eeb458 |
completed | March 27, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69c6d094105881909c5806eb4afa6306 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:13 p.m.