Triple
T31202748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | That's Entertainment! III |
E795518
|
entity |
| Predicate | featuresFilmStudio |
P63931
|
FINISHED |
| Object | Metro-Goldwyn-Mayer |
—
|
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: Metro-Goldwyn-Mayer | Statement: [That's Entertainment! III, featuresFilmStudio, Metro-Goldwyn-Mayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresFilmStudio Context triple: [That's Entertainment! III, featuresFilmStudio, Metro-Goldwyn-Mayer]
-
A.
filmStudioLot
Indicates a relationship where a film studio owns, operates, or is associated with a specific studio lot or production facility.
-
B.
filmStudioInFiction
Indicates that a fictional work features or references a film studio within its narrative or setting.
-
C.
directedFilmForStudio
Indicates that a person directed a film on behalf of, or under contract with, a particular studio.
-
D.
filmStudioParentCompany
Indicates that one company serves as the parent company that owns or controls a given film studio.
-
E.
filmStudioContext
chosen
Indicates a relationship where an entity is involved with, produced by, or contextually associated with a particular film studio.
- F. None of above.
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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a005e8a2f7c819085bfc6f04b866d87 |
completed | May 10, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_6a005de82ef08190a015b385d1d3443c |
completed | May 10, 2026, 10:28 a.m. |
Created at: April 29, 2026, 9:09 p.m.