Triple
T19528166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annweiler am Trifels |
E488586
|
entity |
| Predicate | vehicleRegistrationCode |
P1173
|
FINISHED |
| Object | SÜW |
—
|
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: SÜW | Statement: [Annweiler am Trifels, vehicleRegistrationCode, SÜW]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SÜW Context triple: [Annweiler am Trifels, vehicleRegistrationCode, SÜW]
-
A.
SÜW
chosen
SÜW is the vehicle registration code for the Südliche Weinstraße district in the German state of Rhineland-Palatinate.
-
B.
SWU
SWU is the commonly used abbreviation for Southwest University, a comprehensive higher education institution in China.
-
C.
SOU
SOU is the three-letter National Rail station code for Southampton Central railway station in Hampshire, England.
-
D.
SOU
SOU is the three-letter IATA airport code for Southampton Airport in Hampshire, England.
-
E.
SWC
SWC is the acronym for the South Western Command of the Indian Army, a major operational command responsible for defense and military operations in India’s western sector.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6363d43148190af25caaa57accf9b |
completed | April 20, 2026, 2:20 p.m. |
Created at: April 10, 2026, 1:41 p.m.