Triple
T23782377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Basantar |
E587849
|
entity |
| Predicate | armourLossesIndia |
P153918
|
FINISHED |
| Object | several tanks destroyed or damaged |
—
|
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: several tanks destroyed or damaged | Statement: [Battle of Basantar, armourLossesIndia, several tanks destroyed or damaged]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armourLossesIndia Context triple: [Battle of Basantar, armourLossesIndia, several tanks destroyed or damaged]
-
A.
aircraftLosses
Indicates the number or occurrence of aircraft that have been destroyed, damaged beyond repair, or otherwise lost.
-
B.
numberOfIndianCampaigns
Indicates the count of distinct military or political campaigns that took place in or were directed toward India.
-
C.
warDamage
Indicates damage that was caused as a direct consequence of war or armed conflict.
-
D.
battleStarsWorldWarII
Indicates that the entity has received battle stars for participation in World War II military operations.
-
E.
armamentWWII
Indicates that an entity served as a weapon, piece of equipment, or military hardware used during World War II.
- 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_69e2490f4ad48190b690878eec3596c6 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c62d7c608190b5fd0cf35f5faf42 |
completed | April 29, 2026, 8:49 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f15ed138f88190a8ae555422978908 |
completed | April 29, 2026, 1:28 a.m. |
Created at: April 17, 2026, 7:16 p.m.