Triple
T18193484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Älvsnabben ferry line |
E435600
|
entity |
| Predicate | isUrbanService |
P130175
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Älvsnabben ferry line, isUrbanService, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUrbanService Context triple: [Älvsnabben ferry line, isUrbanService, true]
-
A.
isUrbanNode
Indicates that a location or entity functions as an urban center or node within a city or metropolitan network.
-
B.
isUrbanForm
Indicates that an entity represents or exhibits characteristics of an urban built environment or city-like spatial structure.
-
C.
isUrbanHubFor
Indicates that a location functions as a central urban focal point or primary service center for another area or population.
-
D.
isUrbanSee
Indicates a relationship where a location or area is recognized or classified as an urban settlement or city-like environment.
-
E.
isUrbanDistrict
Indicates that a given district is classified as an urban administrative or residential area rather than a rural one.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e0d12b688190842375dcc5d5537c |
completed | April 19, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f684e48190b38c64b58c518b6a |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:31 a.m.