Triple

T32250090
Position Surface form Disambiguated ID Type / Status
Subject Invincible Iron Man (2016 series) E823856 entity
Predicate inheritsLegacyFrom P165096 FINISHED
Object Tony Stark 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: Tony Stark | Statement: [Invincible Iron Man (2016 series), inheritsLegacyFrom, Tony Stark]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inheritsLegacyFrom
Context triple: [Invincible Iron Man (2016 series), inheritsLegacyFrom, Tony Stark]
  • A. inheritedFrom
    Indicates that one entity has received or derived something (such as traits, rights, or property) from another entity, typically a predecessor or ancestor.
  • B. inheritsMembersFrom chosen
    Indicates that one entity receives or derives its members, properties, or characteristics from another entity.
  • C. inheritsSymbolFrom
    Indicates that one entity derives or receives its symbolic representation or notation from another entity.
  • D. inheritsThrough
    Indicates that one entity acquires rights, traits, or properties from another entity via an intermediate source or lineage rather than directly.
  • E. inheritsMessagePropertyFrom
    Indicates that one message derives or receives a specific property or attribute from another message.
  • 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_69f3490cdda88190a9d61e11252a771f completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6bc3633ec819087f062e1f4bb4813 completed May 3, 2026, 3:08 a.m.
PD Predicate disambiguation batch_69f6b632cf788190a3d0c08cd026b84b completed May 3, 2026, 2:42 a.m.
Created at: May 1, 2026, 12:40 a.m.