Triple
T25578346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odense Station |
E641171
|
entity |
| Predicate | connectsToCityTransport |
P3791
|
FINISHED |
| Object | local buses |
—
|
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: local buses | Statement: [Odense Station, connectsToCityTransport, local buses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsToCityTransport Context triple: [Odense Station, connectsToCityTransport, local buses]
-
A.
hasPublicTransportConnection
chosen
Indicates that there is an available public transportation link or service connecting the related entities.
-
B.
accessibleByPublicTransport
Indicates that a location or entity can be reached using public transportation services such as buses, trains, or trams.
-
C.
hasPublicTransitRole
Indicates that an entity holds a specific functional role or responsibility within a public transit system.
-
D.
hasGoodPublicTransportConnections
Indicates that an entity is well served by public transportation options, providing convenient and efficient connections to other locations.
-
E.
hasFormOfPublicTransit
Indicates that one entity provides or is associated with a particular type or mode of public transportation for another entity or context.
- 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_69e75dc281bc819095ec04dc0c3a94d0 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 21, 2026, 4:02 p.m.