Triple
T4833798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EMI Group |
E108007
|
entity |
| Predicate | tickerSymbol |
P1447
|
FINISHED |
| Object | EMI |
E108006
|
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: EMI | Statement: [EMI Group, tickerSymbol, EMI]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EMI Context triple: [EMI Group, tickerSymbol, EMI]
-
A.
EMI
chosen
EMI was a major British music company and record label group known for signing and distributing many of the world’s leading recording artists.
-
B.
EMF
EMF is the former name of the World Economic Forum, an international organization that engages political, business, and other leaders to shape global, regional, and industry agendas.
-
C.
EMI Blackwood Music
EMI Blackwood Music is a music publishing company that manages and licenses song copyrights for a wide range of artists and recordings.
-
D.
EMD
EMD is the commonly used abbreviation for the Engineering Management Division, a professional group focused on the practice and advancement of engineering management.
-
E.
EMD
EMD is the vehicle registration code assigned to the German town of Emden.
- 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6cca88d88190a8ad6cf7856bdf69 |
completed | March 20, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be4dd744688190a420580e3a8332ff |
completed | March 21, 2026, 7:50 a.m. |
Created at: March 20, 2026, 1:25 p.m.