Triple
T29116593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pizzo Tambo |
E737061
|
entity |
| Predicate | usualRouteType |
P75679
|
FINISHED |
| Object | alpine hiking route |
—
|
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 hiking route | Statement: [Pizzo Tambo, usualRouteType, alpine hiking route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usualRouteType Context triple: [Pizzo Tambo, usualRouteType, alpine hiking route]
-
A.
primaryRouteType
chosen
Indicates the main category or kind of route associated with an entity, such as its primary mode, path, or routing classification.
-
B.
onStandardRouteOf
Indicates that something lies along or follows the usual, predefined, or officially designated route of another entity.
-
C.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
-
D.
primaryRouteThrough
Indicates that one location or path serves as the main or most significant route passing through another location or area.
-
E.
usageRoute
Indicates the path, method, or channel through which something is used, applied, or accessed.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 11:22 a.m.