Triple
T9941227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morelia |
E194084
|
entity |
| Predicate | vehicleRegistrationCode |
P1173
|
FINISHED |
| Object | MIC |
E514351
|
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: MIC | Statement: [Morelia, vehicleRegistrationCode, MIC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MIC Context triple: [Morelia, vehicleRegistrationCode, MIC]
-
A.
MIC
MIC is the commonly used abbreviation for the Mining Industry Committee, a body involved in representing and coordinating interests within the mining sector.
-
B.
MIC
MIC is an FTP security command introduced by RFC 2228 that provides message integrity checking for protected file transfer sessions.
-
C.
MIC
MIC is Japan’s Ministry of Internal Affairs and Communications, the government body responsible for administrative management, local governance, communications, and information policy.
-
D.
Mic
chosen
Mic is the standard astronomical abbreviation for Microscopium, a small constellation in the southern sky.
-
E.
MI
MI is the official two-letter United States Postal Service abbreviation for the state of Michigan.
- 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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb610905c81909d669265c92021a5 |
completed | April 2, 2026, 12:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d229080d0081908b66b9c4166db252 |
completed | April 5, 2026, 9:19 a.m. |
Created at: March 30, 2026, 8:44 p.m.