Triple
T3390465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oranienburger Tor |
E71404
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | BVG |
E353639
|
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: BVG | Statement: [Oranienburger Tor, abbreviation, BVG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BVG Context triple: [Oranienburger Tor, abbreviation, BVG]
-
A.
BVG
chosen
BVG is Berlin’s main public transport company, operating the city’s U-Bahn, trams, buses, and ferries.
-
B.
BVG Projekt GmbH
BVG Projekt GmbH is a subsidiary company of Berlin’s public transport operator that specializes in planning and managing infrastructure and development projects for the city’s transit network.
-
C.
VBG
VBG is the abbreviated name of the German association of botanical gardens, Verband Botanischer Gärten e.V.
-
D.
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.
-
E.
VBB: Berlin AB
VBB: Berlin AB is the central fare zone of Berlin’s public transport network, covering the inner city area served by buses, trams, U-Bahn, and S-Bahn.
- 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb6682c708190b76a7a16cee7c5aa |
completed | March 8, 2026, 5:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b360aded3c8190ab4ca37b4aead1df |
completed | March 13, 2026, 12:56 a.m. |
Created at: March 8, 2026, 3:14 p.m.