Triple
T21999707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tololing |
E543291
|
entity |
| Predicate | strategicRoleIn1999 |
P84296
|
FINISHED |
| Object | Pakistani positions used to shell NH1D |
—
|
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: Pakistani positions used to shell NH1D | Statement: [Tololing, strategicRoleIn1999, Pakistani positions used to shell NH1D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategicRoleIn1999 Context triple: [Tololing, strategicRoleIn1999, Pakistani positions used to shell NH1D]
-
A.
post1989Role
Indicates the role or position an entity held after the year 1989.
-
B.
strategicRoleIn
chosen
Indicates that one entity serves a strategic function, position, or importance within the context, operations, or objectives of another entity.
-
C.
roleAfter2001
Indicates that an entity holds or assumes a particular role or position at some point after the year 2001.
-
D.
strategicRoleDuringWar
Indicates that an entity served a particular strategic function or importance during a specific war or armed conflict.
-
E.
roleAfter2003
Indicates that an entity holds or assumes a particular role or position at some point after the year 2003.
- 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127699a7881908a80b6e9e33fcc0b |
completed | April 28, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:19 p.m.