Triple
T8306637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amstelstation |
E194478
|
entity |
| Predicate | servesBusLine |
P6301
|
FINISHED |
| Object | GVB bus services |
—
|
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: GVB bus services | Statement: [Amstelstation, servesBusLine, GVB bus services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesBusLine Context triple: [Amstelstation, servesBusLine, GVB bus services]
-
A.
hasBusServices
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
-
B.
transportationServedBy
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
-
C.
lineServed
chosen
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.
appliesToTransitLine
Indicates that a rule, condition, or characteristic is specifically associated with and relevant to a particular transit line.
-
E.
accessByBusFrom
Indicates that one location can be reached from another location using a bus as the mode of transportation.
- 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f293db08190912e5e8bb7e940cf |
completed | March 31, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:54 p.m.