Triple
T903290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stockholm Bromma Airport |
E19491
|
entity |
| Predicate | surfaceTransport |
P1379
|
FINISHED |
| Object | bus connections to central Stockholm |
—
|
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: bus connections to central Stockholm | Statement: [Stockholm Bromma Airport, surfaceTransport, bus connections to central Stockholm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceTransport Context triple: [Stockholm Bromma Airport, surfaceTransport, bus connections to central Stockholm]
-
A.
transports
Indicates that one entity carries or conveys another entity from one place to another.
-
B.
transportType
chosen
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
C.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
D.
usesTransport
Indicates that an entity employs or relies on a particular mode or means of transportation to move from one place to another.
-
E.
transportFor
Indicates a relationship where one entity serves as the means or service used to move another entity from one place to another.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad56f4c08190a7a5091ff0eb3209 |
completed | March 1, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69a4aa98caec8190bbcc38320090f058 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.