Triple
T2025165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fürth |
E44190
|
entity |
| Predicate | vehicleRegistrationCode |
P1173
|
FINISHED |
| Object | FÜ |
E14681
|
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: FÜ | Statement: [Fürth, vehicleRegistrationCode, FÜ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FÜ Context triple: [Fürth, vehicleRegistrationCode, FÜ]
-
A.
FÜ
chosen
FÜ is the vehicle registration code used on license plates for the city of Fürth in Bavaria, Germany.
-
B.
FRO
FRO is the three-letter ISO 3166-1 alpha-3 country code assigned to the Faroe Islands.
-
C.
F
F is the New York Stock Exchange ticker symbol for Ford Motor Company, the American multinational automaker known for mass-producing automobiles and pioneering assembly line manufacturing.
-
D.
F
The F is a New York City Subway service that runs along the IND Sixth Avenue Line in Manhattan and Queens Boulevard Line in Queens, connecting Brooklyn, Manhattan, and Queens.
-
E.
Fuhse
Fuhse is a river in Lower Saxony, Germany, that flows through several towns before joining the Aller River.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8f3faa08190a48ae1355d6e009f |
completed | March 7, 2026, 5:34 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae0afa82ac81908c3e3c60c5721536 |
completed | March 8, 2026, 11:49 p.m. |
Created at: March 4, 2026, 7:38 p.m.