Triple
T12006790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manchester International Convention Centre |
E285799
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | MICC |
E285799
|
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: MICC | Statement: [Manchester International Convention Centre, abbreviation, MICC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MICC Context triple: [Manchester International Convention Centre, abbreviation, MICC]
-
A.
MICC
chosen
MICC is an abbreviation for the Manchester International Convention Centre, a major venue in Manchester, England used for conferences, exhibitions, and large events.
-
B.
MiC
MiC is the official abbreviation for Italy’s Ministry of Culture, the government body responsible for cultural heritage, arts, and related policies.
-
C.
MIC
MIC is a major Malaysian political party representing the interests of the Indian community and is a key component of the Barisan Nasional coalition.
-
D.
MIC
MIC is the commonly used abbreviation for the Mining Industry Committee, a body involved in representing and coordinating interests within the mining sector.
-
E.
MIC
MIC is an FTP security command introduced by RFC 2228 that provides message integrity checking for protected file transfer sessions.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903c5cfc08190821e4b2940c51416 |
completed | April 10, 2026, 2:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f48b0574d48190b336a6b9a4ada2a8 |
completed | May 1, 2026, 11:14 a.m. |
Created at: April 8, 2026, 9:46 p.m.