Triple
T8949482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schmölln |
E213307
|
entity |
| Predicate | vehicleRegistrationCode |
P1173
|
FINISHED |
| Object | ABG |
E191603
|
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: ABG | Statement: [Schmölln, vehicleRegistrationCode, ABG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ABG Context triple: [Schmölln, vehicleRegistrationCode, ABG]
-
A.
ABG
chosen
ABG is the vehicle registration code used on license plates for vehicles registered in the Altenburger Land district in Germany.
-
B.
ABG
ABG is a global brand development, marketing, and entertainment company known for owning and managing a large portfolio of consumer brands and intellectual property.
-
C.
ADGB
ADGB was the main federation of free trade unions in Germany during the Weimar Republic, representing millions of workers until its suppression by the Nazi regime.
-
D.
ABY
ABY is the IATA airport code for Southwest Georgia Regional Airport serving Albany, Georgia.
-
E.
ABY
ABY is the station code for Albury railway station, a key regional rail hub in New South Wales, Australia.
- 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_69ca839843408190a39069a029a89f15 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc670b5f50819080f1c73992fe5281 |
completed | April 1, 2026, 12:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfc206550c8190abf016f25b14fa64 |
completed | April 3, 2026, 1:35 p.m. |
Created at: March 30, 2026, 6:59 p.m.