Triple
T30018184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B171 Tiroler Straße |
E762653
|
entity |
| Predicate | hasRouteThroughRegion |
P51005
|
FINISHED |
| Object | Lower Inn Valley |
—
|
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: Lower Inn Valley | Statement: [B171 Tiroler Straße, hasRouteThroughRegion, Lower Inn Valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouteThroughRegion Context triple: [B171 Tiroler Straße, hasRouteThroughRegion, Lower Inn Valley]
-
A.
hasRoadConnectionRegion
Indicates that there is a road-based transportation link connecting one region to another.
-
B.
passesThroughAdministrativeRegion
Indicates that a route, path, or movement crosses into or through the territory of a specified administrative region.
-
C.
includesRouteBetween
Indicates that one entity (such as a service, plan, or network) contains or provides a specific route connecting two locations or points.
-
D.
hasRouteNetwork
Indicates that one entity possesses, is associated with, or is covered by a specific route network connecting multiple locations or paths.
-
E.
routeRegion
chosen
Indicates that a route is located within, passes through, or is associated with a particular geographic region.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: April 29, 2026, 6:46 p.m.