Triple
T20481962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stuttgart Schwabstraße |
E502477
|
entity |
| Predicate | fareZone |
P844
|
FINISHED |
| Object | VVS |
—
|
NE NERFINISHED |
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: VVS | Statement: [Stuttgart Schwabstraße, fareZone, VVS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VVS Context triple: [Stuttgart Schwabstraße, fareZone, VVS]
-
A.
VVS
VVS was the air force branch of the Soviet Union’s armed forces, responsible for military aviation and air defense operations.
-
B.
VVS
chosen
VVS is the public transport association and integrated fare network serving Stuttgart and its surrounding region in Germany.
-
C.
BVVS
BVVS is the commonly used Bulgarian abbreviation for the Bulgarian Air Force, the aerial warfare branch of Bulgaria’s armed forces.
-
D.
VVI
VVI is the IATA airport code for Viru Viru International Airport, the main international gateway serving Santa Cruz de la Sierra, Bolivia.
-
E.
VVSS
VVSS (Vertical Volute Spring Suspension) is an early U.S. tank suspension system using vertical volute springs to support and cushion tracked armored vehicles.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69b57fa9c819091d12320d46a0cee |
completed | April 20, 2026, 9:32 p.m. |
Created at: April 16, 2026, 11:34 a.m.