Triple
T16824047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Köthen |
E408967
|
entity |
| Predicate | vehicleRegistrationCode |
P1173
|
FINISHED |
| Object | ABI |
E504806
|
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: ABI | Statement: [Köthen, vehicleRegistrationCode, ABI]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ABI Context triple: [Köthen, vehicleRegistrationCode, ABI]
-
A.
ABI
chosen
ABI is the vehicle registration code used on license plates for the German town of Bitterfeld-Wolfen.
-
B.
ABI
ABI is the three-letter IATA airport code for Abilene Regional Airport in Abilene, Texas.
-
C.
APIIC
APIIC is a government-owned corporation in Andhra Pradesh, India, responsible for developing industrial infrastructure and promoting industrial growth in the state.
-
D.
AIBN
AIBN (azobisisobutyronitrile) is a commonly used organic radical initiator that thermally decomposes to generate nitrogen gas and carbon-centered radicals for various free-radical reactions.
-
E.
AIB
AIB is a German vehicle registration code used for the district of Rosenheim in Bavaria.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b310ffec81908087e5aaacc4a7c2 |
completed | April 18, 2026, 4:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00b29c170c81908fcc88c31e266ffb |
completed | May 10, 2026, 4:30 p.m. |
Created at: April 10, 2026, 5:23 a.m.