Triple
T21623967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottobeuren |
E533648
|
entity |
| Predicate | vehicleRegistrationCode |
P1173
|
FINISHED |
| Object | MN |
—
|
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: MN | Statement: [Ottobeuren, vehicleRegistrationCode, MN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MN Context triple: [Ottobeuren, vehicleRegistrationCode, MN]
-
A.
MN
MN is the standard two-letter postal abbreviation for the U.S. state of Minnesota.
-
B.
MN
MN is the abbreviated designation commonly used for a Monumento Nacional, a protected national monument of significant cultural or historical value.
-
C.
MN
chosen
MN is the regional vehicle registration code assigned to the district of Unterallgäu in Bavaria, Germany.
-
D.
MN
MN is the abbreviated name for Mobilier National, the French national agency responsible for preserving, managing, and furnishing state-owned collections of furniture and decorative arts.
-
E.
MN
MN is the vehicle registration code used on license plates for County Monaghan in Ireland.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef521125f481909ccfc95d884976e2 |
completed | April 27, 2026, 12:09 p.m. |
Created at: April 16, 2026, 6:34 p.m.