Triple
T13070345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rokin metro station |
E329438
|
entity |
| Predicate | operatedBy |
P86
|
FINISHED |
| Object | GVB |
E28406
|
NE 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 | Statement: [Rokin metro station, operatedBy, GVB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GVB Context triple: [Rokin metro station, operatedBy, GVB]
-
A.
GVB
chosen
GVB is Amsterdam’s primary public transport company, operating the city’s trams, buses, metro, and ferries.
-
B.
GVB Amsterdam
GVB Amsterdam is the primary public transport operator in Amsterdam, running the city’s trams, buses, metros, and ferries.
-
C.
GVB bus network
The GVB bus network is Amsterdam’s municipal bus system, providing extensive urban and regional public transport connections throughout the city and surrounding areas.
-
D.
GVB zone 5711
GVB zone 5711 is a public transport fare zone in Amsterdam that includes Bullewijk metro station within the GVB ticketing system.
-
E.
GVB Tram
GVB Tram is the tram network operated by Amsterdam’s municipal public transport company, providing urban rail services throughout the city and surrounding areas.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d980ee6130819095d835e7ff6a8c5b |
completed | April 10, 2026, 10:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6d60510dc81909e0cba8b63a50d9c |
completed | May 3, 2026, 4:58 a.m. |
Created at: April 9, 2026, 9 p.m.