Triple
T33116826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hairatan border crossing |
E847479
|
entity |
| Predicate | borderSecurityManagedBy |
P36604
|
FINISHED |
| Object | Afghan authorities |
—
|
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: Afghan authorities | Statement: [Hairatan border crossing, borderSecurityManagedBy, Afghan authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderSecurityManagedBy Context triple: [Hairatan border crossing, borderSecurityManagedBy, Afghan authorities]
-
A.
borderGuardDuty
Indicates that an entity is assigned to perform security or monitoring duties at a border or checkpoint.
-
B.
oppositeSideBorderControlManagedBy
Indicates that the border control operations on the opposite side of a border crossing are administered or overseen by a specified authority or organization.
-
C.
borderControls
chosen
Indicates that one entity enforces or administers border control measures over another entity or at a specific boundary.
-
D.
borderMonitored
Indicates that a border between two regions or entities is actively being watched, controlled, or surveilled.
-
E.
borderControlCoordinatedWith
Indicates that one entity coordinated its border control activities or policies with another entity.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff2636e2bc8190bba91eff91431c6e |
completed | May 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69ff25c65be48190868480d94e1c4e89 |
completed | May 9, 2026, 12:17 p.m. |
Created at: May 1, 2026, 1:27 a.m.