Triple
T24072379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Phillora |
E596268
|
entity |
| Predicate | forcePakistan |
P153916
|
FINISHED |
| Object | 6th Armoured Division (Pakistan) |
—
|
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: 6th Armoured Division (Pakistan) | Statement: [Battle of Phillora, forcePakistan, 6th Armoured Division (Pakistan)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forcePakistan Context triple: [Battle of Phillora, forcePakistan, 6th Armoured Division (Pakistan)]
-
A.
unitInvolvedPakistan
chosen
Indicates that a unit is involved in or associated with activities, operations, or events in Pakistan.
-
B.
commanderPakistan
Indicates that one entity serves as the military or organizational commander of 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.
areaRankInPakistan
Indicates the relative position of an entity when all entities in Pakistan are ordered by their area size.
-
E.
populationRankInPakistan
Indicates the relative position of an entity in terms of its population size compared to other entities within Pakistan.
- 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_69e288c3999c8190809b282a04813dec |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1db1aad248190a1d25c64cc5016eb |
completed | April 29, 2026, 10:19 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:42 p.m.