Triple
T4230189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flughafen |
E94560
|
entity |
| Predicate | fareZone |
P844
|
FINISHED |
| Object | VGN |
E90420
|
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: VGN | Statement: [Flughafen, fareZone, VGN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VGN Context triple: [Flughafen, fareZone, VGN]
-
A.
VGN
chosen
VGN (Verkehrsverbund Großraum Nürnberg) is the public transport association that coordinates and manages integrated ticketing and services across the greater Nuremberg metropolitan area in Germany.
-
B.
B-VG
B-VG is the commonly used abbreviation for Austria’s Federal Constitutional Law, which forms the core of the country’s constitutional framework.
-
C.
VRN
VRN is the public transport association serving Germany’s Rhine-Neckar metropolitan region, coordinating regional and local transit services across multiple states.
-
D.
VBG
VBG is the abbreviated name of the German association of botanical gardens, Verband Botanischer Gärten e.V.
-
E.
VG
VG is the two-letter ISO 3166 country code assigned to the British Virgin Islands.
- 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_69b3453700a08190ae88792e3dc63207 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e61ccc081909b880baf1d6a0f24 |
completed | March 12, 2026, 11:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5964f364881908c53cd46af6b1e98 |
completed | March 14, 2026, 5:09 p.m. |
Created at: March 12, 2026, 11:05 p.m.