Triple
T24015529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Asal Uttar |
E594661
|
entity |
| Predicate | PakistaniEquipmentUsed |
P125036
|
FINISHED |
| Object | M48 Patton tanks |
—
|
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: M48 Patton tanks | Statement: [Battle of Asal Uttar, PakistaniEquipmentUsed, M48 Patton tanks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PakistaniEquipmentUsed Context triple: [Battle of Asal Uttar, PakistaniEquipmentUsed, M48 Patton tanks]
-
A.
unitInvolvedPakistan
Indicates that a unit is involved in or associated with activities, operations, or events in Pakistan.
-
B.
armourLossesPakistan
Indicates the number or extent of armored military equipment lost by Pakistan.
-
C.
PakistaniResponse
Indicates a response, reaction, or action taken by Pakistan or Pakistani authorities in relation to a preceding event, request, or situation.
-
D.
commanderPakistan
Indicates that one entity serves as the military or organizational commander of Pakistan.
-
E.
concludedWeaponSystemUsed
chosen
Indicates that it has been inferred or determined that a particular weapon system was used in the related event or action.
- 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_69e288bc8f608190ac4af29f0bd1c744 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d5a32374819094dcb42abf18c033 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:42 p.m.