Triple
T20791219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kårsta |
E511781
|
entity |
| Predicate | railwayTerminusType |
P27765
|
FINISHED |
| Object | northern terminus |
—
|
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: northern terminus | Statement: [Kårsta, railwayTerminusType, northern terminus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayTerminusType Context triple: [Kårsta, railwayTerminusType, northern terminus]
-
A.
railTerminus
Indicates that a railway line or service ends at a particular station or location, which serves as its final terminus.
-
B.
passengerTerminalType
Indicates the specific kind or category of passenger terminal associated with an entity.
-
C.
railroadTerminusFor
Indicates that one location serves as the end point or final station of a particular railroad line for another location.
-
D.
railwayStationCategory
Indicates the classification or type category assigned to a railway station within a rail network or system.
-
E.
stationType
chosen
Indicates the specific category or classification of a station based on its function, services, or operational characteristics.
- 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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c29010508190bf2cf577d7f64754 |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0575b1c81908d010223fcd1213e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:38 p.m.