Triple
T35504152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mehamn Airport |
E1026094
|
entity |
| Predicate | servedByRouteType |
P13326
|
FINISHED |
| Object | regional routes |
—
|
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: regional routes | Statement: [Mehamn Airport, servedByRouteType, regional routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByRouteType Context triple: [Mehamn Airport, servedByRouteType, regional routes]
-
A.
servesAsRouteTo
Indicates that one entity functions as a pathway, channel, or means of access leading to another entity.
-
B.
servedByLineType
Indicates that a service, stop, or route is operated or covered by a specific type of transit line.
-
C.
servedByStateRoute
Indicates that a location, facility, or area is provided access or transportation service by a particular state route.
-
D.
hasRouteType
chosen
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
-
E.
servedByNationalRoute
Indicates that a location or facility is connected to and accessible via a specified national route.
- 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_69f76dfc9c60819089c4217d93922615 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0010e46d948190a51111b5270fade7 |
completed | May 10, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_6a001061d34c8190bfe73f3d7c061eb7 |
completed | May 10, 2026, 4:58 a.m. |
Created at: May 3, 2026, 4:04 p.m.