Triple
T2424513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iran–Pakistan border |
E53493
|
entity |
| Predicate | borderManagement |
P3948
|
FINISHED |
| Object | fencing projects |
—
|
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: fencing projects | Statement: [Iran–Pakistan border, borderManagement, fencing projects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderManagement Context triple: [Iran–Pakistan border, borderManagement, fencing projects]
-
A.
borderControlSide
Indicates that one entity is positioned on or associated with a particular side or segment of a border control area or checkpoint.
-
B.
borderControls
Indicates that one entity enforces or administers border control measures over another entity or at a specific boundary.
-
C.
borderRegime
chosen
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
-
D.
borderEstablished
Indicates that a formal boundary between two geographic or political entities has been officially defined and put into effect.
-
E.
hasBorderControlStatus
Indicates the type or condition of border control that applies to a given entity or location.
- 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_69ab495c44d48190b7235b23719bc3f6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc9f342e88190a430b02842ded418 |
completed | March 7, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69abc5a889948190b77de4ef6ac815a8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 6, 2026, 9:42 p.m.