Triple
T16410820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esslingen am Neckar |
E398557
|
entity |
| Predicate | vehicleRegistrationCode |
P1173
|
FINISHED |
| Object | ES |
E483341
|
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: ES | Statement: [Esslingen am Neckar, vehicleRegistrationCode, ES]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ES Context triple: [Esslingen am Neckar, vehicleRegistrationCode, ES]
-
A.
ES
ES is the ticker symbol for the E-mini S&P 500 futures contract, a widely traded equity index derivative on the Chicago Mercantile Exchange used for hedging and speculating on the S&P 500.
-
B.
ES
ES is the commonly used abbreviation for European Solidarity, a Polish political party.
-
C.
ES
ES is the ISO 3166-1 alpha-2 country code for Spain, a European nation on the Iberian Peninsula.
-
D.
ES
chosen
ES is the vehicle registration code for the district of Esslingen in the Stuttgart region of Baden-Württemberg, Germany.
-
E.
ESP
ESP is the three-letter FIFA country code used to represent the Spain national football team in international competitions and official records.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328731a408190b38dcab0b7bb65ff |
completed | April 18, 2026, 6:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a003c66d41481909340f247f6e5393f |
completed | May 10, 2026, 8:05 a.m. |
Created at: April 10, 2026, 5:09 a.m.