Triple

T34672355
Position Surface form Disambiguated ID Type / Status
Subject Time Stone E890407 entity
Predicate creatorInMCU P199755 FINISHED
Object Unknown cosmic entities 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: Unknown cosmic entities | Statement: [Time Stone, creatorInMCU, Unknown cosmic entities]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: creatorInMCU
Context triple: [Time Stone, creatorInMCU, Unknown cosmic entities]
  • A. creatorInComics
    Indicates that one entity is the creator (such as writer or artist) responsible for the content or characters appearing in a particular comic work or series.
  • B. characterNameInMCU
    Indicates that a given character is known by a particular name within the Marvel Cinematic Universe (MCU) continuity.
  • C. marvelCinematicUniverseDebutFilm
    Indicates the film in which an entity (such as a character or actor) first appeared within the Marvel Cinematic Universe.
  • D. creatorOfCharacter
    Indicates that one entity is the originator or author who created or conceived the other entity as a character.
  • E. MCUFamily
    Indicates a familial relationship between entities within the Marvel Cinematic Universe (MCU), such as by blood, marriage, or adoption.
  • 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_69f349d9c59481908b36baa0be093aea completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69ff53389a0481908b2baeb43c6294f0 completed May 9, 2026, 3:31 p.m.
PD Predicate disambiguation batch_69ff52e2b4b88190b38d160d771fe14b completed May 9, 2026, 3:29 p.m.
PDg Predicate description generation batch_69ff5337e6f88190ae0418335477063c completed May 9, 2026, 3:31 p.m.
Created at: May 1, 2026, 2:05 a.m.