Triple
T16021086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Sky |
E388597
|
entity |
| Predicate | distributor |
P1951
|
FINISHED |
| Object | MGM |
E10100
|
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: MGM | Statement: [Blue Sky, distributor, MGM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MGM Context triple: [Blue Sky, distributor, MGM]
-
A.
MGM
chosen
MGM (Metro-Goldwyn-Mayer) is a historic American film studio renowned for its iconic roaring lion logo and for producing many of the most famous movies of Hollywood’s Golden Age.
-
B.
MGM
MGM is a major American entertainment and hospitality brand best known for its iconic casinos, resorts, and film studio legacy.
-
C.
MGM
MGM is the IATA airport code for Montgomery Regional Airport, the primary commercial airport serving Montgomery, Alabama.
-
D.
MGM
MGM is the three-letter FAA location identifier assigned to Harbor Springs Municipal Airport in Michigan.
-
E.
MGM Holdings
MGM Holdings is the parent company that owns and oversees Metro-Goldwyn-Mayer’s entertainment assets and operations.
- 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_69d86dabcb7c8190b6a39d6831d2fa1b |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e183231f2c81908f4e4037c3aa180b |
completed | April 17, 2026, 12:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffcf2c6128819091d8f3710578834e |
completed | May 10, 2026, 12:19 a.m. |
Created at: April 10, 2026, 4:55 a.m.