Triple
T23782356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Basantar |
E587849
|
entity |
| Predicate | unitInvolvedPakistan |
P153916
|
FINISHED |
| Object | 8 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: 8 Infantry Division | Statement: [Battle of Basantar, unitInvolvedPakistan, 8 Infantry Division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unitInvolvedPakistan Context triple: [Battle of Basantar, unitInvolvedPakistan, 8 Infantry Division]
-
A.
governingAuthorityPakistaniSide
Indicates that an entity serves as the governing authority or administrative body on the Pakistani side of a border, region, or bilateral context.
-
B.
isInPakistan
Indicates that the subject is located within the geographical boundaries of Pakistan.
-
C.
statusInPakistan
Indicates the legal, social, or operational condition or standing that something or someone has within the context of Pakistan.
-
D.
PakistaniResponse
Indicates a response, reaction, or action taken by Pakistan or Pakistani authorities in relation to a preceding event, request, or situation.
-
E.
entryPointFromPakistan
Indicates that something serves as a point of entry originating from Pakistan.
- 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.