Triple
T27524101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AH1 |
E694787
|
entity |
| Predicate | borderCrossingAtWesternEnd |
P4105
|
FINISHED |
| Object | Turkey–Bulgaria border |
—
|
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: Turkey–Bulgaria border | Statement: [AH1, borderCrossingAtWesternEnd, Turkey–Bulgaria border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCrossingAtWesternEnd Context triple: [AH1, borderCrossingAtWesternEnd, Turkey–Bulgaria border]
-
A.
borderCrossingRouteTo
Indicates a route or path used to travel across a border from one place or jurisdiction to another.
-
B.
hasBorderCrossingSide
Indicates that one side of a border crossing is associated with or located on a particular boundary or segment of that crossing.
-
C.
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.
-
D.
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.
-
E.
borderCrossingArea
Indicates an area specifically designated for crossing a border between two jurisdictions or territories.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 27, 2026, 1:23 p.m.