Triple
T34283937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Südbahnhof (Frankfurt am Main) |
E879678
|
entity |
| Predicate | hasBusLine |
P39381
|
FINISHED |
| Object | bus line 36 |
—
|
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 line 36 | Statement: [Südbahnhof (Frankfurt am Main), hasBusLine, bus line 36]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusLine Context triple: [Südbahnhof (Frankfurt am Main), hasBusLine, bus line 36]
-
A.
hasBusServices
chosen
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
-
B.
hasTrolleybusLine
Indicates that there exists a trolleybus service or route connecting the related entities.
-
C.
hasBRTLine
Indicates that a bus rapid transit (BRT) line is present, operates on, or serves the referenced entity.
-
D.
hasTramTrainLine
Indicates that there exists a tram-train line connection or service linking the related entities.
-
E.
hasChronobusLine
Indicates that a location or entity is served by, or connected to, a Chronobus transit line.
- 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 1, 2026, 1:57 a.m.