Triple
T32344056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zaranj District |
E826404
|
entity |
| Predicate | borderInfrastructureRole |
P108134
|
FINISHED |
| Object | hosts customs and border facilities near Iran |
—
|
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: hosts customs and border facilities near Iran | Statement: [Zaranj District, borderInfrastructureRole, hosts customs and border facilities near Iran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderInfrastructureRole Context triple: [Zaranj District, borderInfrastructureRole, hosts customs and border facilities near Iran]
-
A.
borderRegionRole
Indicates a role or function that an entity has specifically in relation to a border region or border area.
-
B.
borderFacilityFunction
chosen
Indicates the functional role or purpose that a particular facility serves in the context of a border or border-crossing operation.
-
C.
bordersFacility
Indicates that one facility or site lies directly adjacent to and shares a boundary with another facility.
-
D.
borderGuardDuty
Indicates that an entity is assigned to perform security or monitoring duties at a border or checkpoint.
-
E.
borderRegime
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
- 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feff70fbec8190b1ff5f943f29613e |
completed | May 9, 2026, 9:33 a.m. |
| PD | Predicate disambiguation | batch_69fefbcd5b7881909cfe52b32f8a4301 |
completed | May 9, 2026, 9:18 a.m. |
Created at: May 1, 2026, 12:48 a.m.