Triple
T22239743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XETR |
E549688
|
entity |
| Predicate | isA |
P310
|
FINISHED |
| Object | MIC |
—
|
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: MIC | Statement: [XETR, isA, MIC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MIC Context triple: [XETR, isA, 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 the vehicle registration code used on license plates issued in the Mexican state of Michoacán de Ocampo.
-
D.
MIC
MIC is a third-level Catholic college of education and the liberal arts located in Limerick, Ireland.
-
E.
MIC
chosen
MIC is a standardized four-character code used globally to uniquely identify securities trading venues such as stock exchanges and alternative trading systems.
- 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f132133b908190b0fb32a5ee68e1e6 |
completed | April 28, 2026, 10:17 p.m. |
Created at: April 16, 2026, 8:38 p.m.