Triple
T15551483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Széll Kálmán tér |
E370753
|
entity |
| Predicate | busLineServed |
P39381
|
FINISHED |
| Object | multiple BKK bus lines |
—
|
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: multiple BKK bus lines | Statement: [Széll Kálmán tér, busLineServed, multiple BKK bus lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: busLineServed Context triple: [Széll Kálmán tér, busLineServed, multiple BKK bus lines]
-
A.
transportationServedBy
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
-
B.
hasBusServices
chosen
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
-
C.
lineServed
Indicates that a particular transportation line (such as a bus, train, or metro line) provides service to or is operated at a given stop, station, or route segment.
-
D.
servesCommuterRailLine
Indicates that a location or facility provides access to and is a stop or station for a commuter rail line.
-
E.
appliesToTransitLine
Indicates that a rule, condition, or characteristic is specifically associated with and relevant to a particular 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04a9551288190a583e8291c35f521 |
completed | April 16, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:08 a.m.