Triple
T5779540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mumbai Indians |
E127521
|
entity |
| Predicate | nickname |
P55
|
FINISHED |
| Object | MI |
E546257
|
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: MI | Statement: [Mumbai Indians, nickname, MI]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MI Context triple: [Mumbai Indians, nickname, MI]
-
A.
MI
MI is the official two-letter United States Postal Service abbreviation for the state of Michigan.
-
B.
MI
chosen
MI is the commonly used abbreviation for the Mumbai Indians, a prominent franchise cricket team in the Indian Premier League.
-
C.
Mi
Mi is a sub-brand of Xiaomi used primarily for its line of consumer electronics and smart devices, including smartphones, TVs, and streaming boxes.
-
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_69c008361fa88190aefa4dc41b051e7f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029e26ff88190b7f8eb03bcd30dc6 |
completed | March 22, 2026, 5:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0980d833481908e69a80a63bbe256 |
completed | March 23, 2026, 1:31 a.m. |
Created at: March 22, 2026, 3:50 p.m.