Triple
T10933202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angur Ada |
E258260
|
entity |
| Predicate | conflictRelevance |
P47615
|
FINISHED |
| Object | has been affected by Afghanistan–Pakistan border security issues |
—
|
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: has been affected by Afghanistan–Pakistan border security issues | Statement: [Angur Ada, conflictRelevance, has been affected by Afghanistan–Pakistan border security issues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictRelevance Context triple: [Angur Ada, conflictRelevance, has been affected by Afghanistan–Pakistan border security issues]
-
A.
conflictSpecific
Indicates a specific, concrete instance or type of conflict that exists between the related entities.
-
B.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
C.
conflictRelatedStatus
chosen
Indicates a status or condition that is directly associated with, affected by, or resulting from a conflict.
-
D.
conflictIntroduced
Indicates that a conflict has been newly created or brought into existence between the related entities.
-
E.
conflictDescribedIn
Indicates that a particular conflict is documented, detailed, or discussed within a specified information source or description.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770a16cbc8190acd619defed7114c |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d72e799f808190b6ab64fc7586a303 |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.