Triple
T23782351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Basantar |
E587849
|
entity |
| Predicate | unitInvolvedIndia |
P39448
|
FINISHED |
| Object | 54 Infantry Division |
—
|
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: 54 Infantry Division | Statement: [Battle of Basantar, unitInvolvedIndia, 54 Infantry Division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unitInvolvedIndia Context triple: [Battle of Basantar, unitInvolvedIndia, 54 Infantry Division]
-
A.
IndianCenter
Indicates that something serves as a central or primary hub related to India or Indian affairs.
-
B.
armedForcesInvolved
chosen
Indicates that the relationship or event involves the participation or presence of military or armed forces.
-
C.
involvedForcesType
Indicates the type or category of forces that participate in or are associated with a given event, interaction, or situation.
-
D.
governingAuthorityIndianSide
Indicates that one entity serves as the official governing authority or administrative body on the Indian side in a cross-border or bilateral context.
-
E.
IndianOperation
Indicates an operation, activity, or action that is carried out in, associated with, or specifically related to India.
- 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_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. |
Created at: April 17, 2026, 7:16 p.m.