Triple
T17715855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tell Abyad |
E442196
|
entity |
| Predicate | isBorderCrossingPoint |
P4105
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tell Abyad, isBorderCrossingPoint, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBorderCrossingPoint Context triple: [Tell Abyad, isBorderCrossingPoint, yes]
-
A.
hasBorderCrossingFunction
Indicates that an entity serves as a location or facility where people, goods, or vehicles can legally cross a border between jurisdictions.
-
B.
hasBorderCrossing
chosen
Indicates that there exists a point or facility where movement or transit is possible between the boundaries of two adjacent regions or jurisdictions.
-
C.
hasRailBorderCrossing
Indicates that two places are connected by at least one official border crossing that is served by rail transport.
-
D.
crossesBorderOf
Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
-
E.
isPartOfBorderCrossingCorridor
Indicates that something lies within or contributes to the designated route or area used for crossing a border.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47480955481908fa0d3d34aaedd48 |
completed | April 19, 2026, 6:21 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:06 a.m.