Triple
T5083129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amsterdam Metro line 50 |
E114571
|
entity |
| Predicate | operator |
P179
|
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: [Amsterdam Metro line 50, operator, GVB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GVB Context triple: [Amsterdam Metro line 50, operator, GVB]
-
A.
GVB
chosen
GVB is Amsterdam’s primary public transport company, operating the city’s trams, buses, metro, and ferries.
-
B.
VBB
VBB is the public transport authority and fare network that coordinates and integrates regional and urban transit services across Berlin and the surrounding Brandenburg region.
-
C.
GVA
GVA is the IATA airport code for Geneva Airport, the international airport serving Geneva, Switzerland and the surrounding region.
-
D.
VBG
VBG is the abbreviated name of the German association of botanical gardens, Verband Botanischer Gärten e.V.
-
E.
BVG
BVG is Berlin’s main public transport company, operating the city’s U-Bahn, trams, buses, and ferries.
- 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_69bd443dbf908190a9401e9c2dc7bd7d |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7517af308190bab5507a9344bf68 |
completed | March 20, 2026, 4:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69beba6f3eb48190b544bf743829cb0c |
completed | March 21, 2026, 3:34 p.m. |
Created at: March 20, 2026, 1:39 p.m.