Triple
T14475117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Piranha |
E358946
|
entity |
| Predicate | casualtiesAndLosses_VietCongKilled |
P114790
|
FINISHED |
| Object | over 170 |
—
|
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: over 170 | Statement: [Operation Piranha, casualtiesAndLosses_VietCongKilled, over 170]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesAndLosses_VietCongKilled Context triple: [Operation Piranha, casualtiesAndLosses_VietCongKilled, over 170]
-
A.
estimatedNorthVietnameseCasualties
Indicates the reported or calculated number of casualties attributed to North Vietnamese forces in a given context or event.
-
B.
numberOfVictimsKilled
Indicates the count of victims who were killed as a result of the referenced event or action.
-
C.
casualtiesTexianKilled
Indicates that the relationship specifies the number of Texian individuals who were killed as casualties in a particular event or conflict.
-
D.
opponentInBattleOfIaDrang
Indicates that one entity served as an opposing force to another in the Battle of Ia Drang.
-
E.
estimatedPrisonersKilled
Indicates the estimated number of prisoners who were killed in a given context or event.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91fc1fc48190842b09aa03ba79f8 |
completed | April 14, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de610330a48190b558235a14c0dc9f |
completed | April 14, 2026, 3:45 p.m. |
Created at: April 10, 2026, 1:20 a.m.