Triple

T35624025
Position Surface form Disambiguated ID Type / Status
Subject Metrocolor E1029397 entity
Predicate usedInCreditsAs P66001 FINISHED
Object Photographed in Metrocolor 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: Photographed in Metrocolor | Statement: [Metrocolor, usedInCreditsAs, Photographed in Metrocolor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedInCreditsAs
Context triple: [Metrocolor, usedInCreditsAs, Photographed in Metrocolor]
  • A. usedInClosingCreditsOf
    Indicates that something is listed or acknowledged in the closing credits of a work (such as a film, show, or game).
  • B. usedInSeasonOpeningCreditsOf
    Indicates that something (such as an image, clip, or element) appears in and is utilized as part of the opening credits sequence of a particular season of a show.
  • C. creditedIn chosen
    Indicates that an entity is acknowledged or listed as a contributor or source within a particular work, record, or context.
  • D. wasUsedBy
    Indicates that something served as a tool, resource, or means for an agent to perform an action or achieve a result.
  • E. alsoUsedIn
    Indicates that something is additionally employed, applied, or present in another context, setting, or use case beyond the primary one.
  • 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_69f76e0709408190bbe322bf1707ef6b completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fed6da0390819096b88ef4714b144e completed May 9, 2026, 6:40 a.m.
PD Predicate disambiguation batch_69fed53517d081909966f31707625f1a completed May 9, 2026, 6:33 a.m.
Created at: May 3, 2026, 4:05 p.m.