Triple
T3658521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slovenia–Italy border |
E77592
|
entity |
| Predicate | hasTransportCrossing |
P4105
|
FINISHED |
| Object | road border crossings |
—
|
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: road border crossings | Statement: [Slovenia–Italy border, hasTransportCrossing, road border crossings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransportCrossing Context triple: [Slovenia–Italy border, hasTransportCrossing, road border crossings]
-
A.
hasBridgeTypeCrossing
Indicates that a bridge is characterized by a specific type of crossing it provides or supports.
-
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.
hasMajorCrossing
Indicates that one entity has a significant or primary intersection or crossing with another entity.
-
D.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
E.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
- 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_69ad85dfc4dc8190a441864202ab2a7a |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3d48a2081908ac0f76d548a53ee |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb847e9d881909dad2ffd0f3b6c15 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.