Triple

T14918793
Position Surface form Disambiguated ID Type / Status
Subject Vitas E371452 entity
Predicate knownForStagePersona P70717 FINISHED
Object eccentric futuristic image 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: eccentric futuristic image | Statement: [Vitas, knownForStagePersona, eccentric futuristic image]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: knownForStagePersona
Context triple: [Vitas, knownForStagePersona, eccentric futuristic image]
  • A. stagePersonaOf chosen
    Indicates a relationship where one entity is the staged or performed persona, role, or character representation of another entity.
  • B. knownForStoryline
    Indicates that an entity is recognized or notable specifically for its narrative or storyline.
  • C. namedForKnownFor
    Indicates that one entity is named after another entity specifically because that other entity is notable or recognized for something.
  • D. knownPrimarilyThrough
    Indicates that one entity is chiefly recognized, identified, or made familiar to others by means of another entity (such as a work, role, medium, or context).
  • E. segmentKnownFor
    Indicates that a specific segment or portion of something is recognized or notable for a particular characteristic, feature, or association.
  • 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_69d85cc7ea3481908228b5acb7d06f12 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded62f76bc81909ebc8899096cd1a0 completed April 15, 2026, 12:05 a.m.
PD Predicate disambiguation batch_69de9a52ba988190a26e268b4ea083ea completed April 14, 2026, 7:49 p.m.
Created at: April 10, 2026, 2:33 a.m.