Triple

T2541815
Position Surface form Disambiguated ID Type / Status
Subject Amazon MGM Studios E57800 entity
Predicate hasRightsOver P39434 FINISHED
Object MGM film library LITERAL 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 film library | Statement: [Amazon MGM Studios, hasRightsOver, MGM film library]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRightsOver
Context triple: [Amazon MGM Studios, hasRightsOver, MGM film library]
  • A. hasAccessTo
    Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
  • B. hasLimitedAuthorityOver
    Indicates that one entity holds a constrained or partial power to direct, control, or make decisions about another entity, but not full or unrestricted authority.
  • C. canOverrule
    Indicates that one entity has the authority or power to reverse, nullify, or supersede the decision or judgment made by another entity.
  • D. hasLegalAuthorityFrom
    Indicates that one entity possesses formal legal power, rights, or authorization that originates from or is granted by another entity.
  • E. hasAuthorityControl
    Indicates that one entity possesses formal power, control, or decision-making authority over another entity or activity.
  • F. None of above. chosen

Provenance (4 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_69ab4a5212d88190b989ce129f2ad87f completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abd2bd92f88190bf100c799f62210c completed March 7, 2026, 7:24 a.m.
PD Predicate disambiguation batch_69abd0c63964819092d5f578195ae8dd completed March 7, 2026, 7:16 a.m.
PDg Predicate description generation batch_69abd1c7b6e48190be9a0c31069df797 completed March 7, 2026, 7:20 a.m.
Created at: March 6, 2026, 9:47 p.m.