Triple
T24531522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Route 215-CH |
E606822
|
entity |
| Predicate | borderPass |
P156626
|
FINISHED |
| Object | Cardenal Samoré Pass |
—
|
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: Cardenal Samoré Pass | Statement: [Route 215-CH, borderPass, Cardenal Samoré Pass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderPass Context triple: [Route 215-CH, borderPass, Cardenal Samoré Pass]
-
A.
borderStation
Indicates a facility or checkpoint located at or near a border where cross-boundary movement, control, or processing of people or goods occurs.
-
B.
borderPostIs
Indicates that one entity functions as a border post associated with or located at another entity.
-
C.
borderPostType
Indicates the specific kind or classification of a border post associated with a boundary or crossing point.
-
D.
borderStationFor
Indicates that a particular border station serves, monitors, or is responsible for a specific border crossing or boundary segment.
-
E.
borderOpening
Indicates that a border between two regions is being opened or made accessible for crossing or interaction.
- F. None of above. chosen
Provenance (4 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_69e2c4c90c848190b23c4303620dcaaf |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:25 a.m.