Triple
T19681104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikołów |
E472587
|
entity |
| Predicate | hasVehicleRegistrationCode |
P1173
|
FINISHED |
| Object | SMI |
—
|
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: SMI | Statement: [Mikołów, hasVehicleRegistrationCode, SMI]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SMI Context triple: [Mikołów, hasVehicleRegistrationCode, SMI]
-
A.
SMI
SMI is the IATA airport code for Samos International Airport, the main air gateway to the Greek island of Samos.
-
B.
SMI
SMI is the station code used to designate the Smithsonian Metro station in Washington, D.C.'s rapid transit system.
-
C.
SMI
SMI is the Swiss Market Index, a leading stock market index that tracks the performance of major blue-chip companies listed on the SIX Swiss Exchange.
-
D.
SMI
chosen
SMI is the vehicle registration code assigned to the town of Mikołów in Poland.
-
E.
SMIT
SMIT (System Management Interface Tool) is IBM AIX’s menu-driven administrative interface used to simplify and standardize system management tasks.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e641bf97348190bc31b00ed4ec6cad |
completed | April 20, 2026, 3:09 p.m. |
Created at: April 10, 2026, 1:45 p.m.