Triple
T33191007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nusaybin |
E849609
|
entity |
| Predicate | borderGateWith |
P46215
|
FINISHED |
| Object | Qamishli border crossing |
—
|
NE NERFINISHED |
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: Qamishli border crossing | Statement: [Nusaybin, borderGateWith, Qamishli border crossing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderGateWith Context triple: [Nusaybin, borderGateWith, Qamishli border crossing]
-
A.
borderStationFor
Indicates that a particular border station serves, monitors, or is responsible for a specific border crossing or boundary segment.
-
B.
borderStation
chosen
Indicates a facility or checkpoint located at or near a border where cross-boundary movement, control, or processing of people or goods occurs.
-
C.
borderPass
Indicates that one entity crosses or moves through the boundary separating two regions or jurisdictions.
-
D.
borderControls
Indicates that one entity enforces or administers border control measures over another entity or at a specific boundary.
-
E.
borderOpening
Indicates that a border between two regions is being opened or made accessible for crossing or interaction.
- 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff2d22ffb48190ae58ddf3c7e02869 |
completed | May 9, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69ff2ac2e1c4819096cc64e94aef2ff0 |
completed | May 9, 2026, 12:38 p.m. |
Created at: May 1, 2026, 1:29 a.m.