Triple
T21487766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altdorf |
E530157
|
entity |
| Predicate | isTransitPointFor |
P128427
|
FINISHED |
| Object | Alpine passes |
—
|
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: Alpine passes | Statement: [Altdorf, isTransitPointFor, Alpine passes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTransitPointFor Context triple: [Altdorf, isTransitPointFor, Alpine passes]
-
A.
isTransitPointOn
chosen
Indicates that one location serves as an intermediate transit point along a specified route, path, or journey.
-
B.
isMajorTransitPointFor
Indicates that a location serves as a primary hub or key node for the movement or transfer of people, goods, or vehicles within a transportation network.
-
C.
isTouristTransitPoint
Indicates that a location serves as a transit hub or intermediate stop primarily used by tourists while traveling between destinations.
-
D.
wasTransitPointOn
Indicates that something served as an intermediate stop or passage location along a specified route, journey, or transport path.
-
E.
appliesToTransitStation
Indicates that something (such as a rule, feature, condition, or attribute) is specifically relevant or applicable to a transit station.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea37e25c81909ae185fcab19bc4b |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:22 p.m.