Triple

T32117277
Position Surface form Disambiguated ID Type / Status
Subject Ned Leeds (MCU) E820271 entity
Predicate hasMagicPotential P202397 FINISHED
Object yes (implied in Spider-Man: No Way Home) 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: yes (implied in Spider-Man: No Way Home) | Statement: [Ned Leeds (MCU), hasMagicPotential, yes (implied in Spider-Man: No Way Home)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMagicPotential
Context triple: [Ned Leeds (MCU), hasMagicPotential, yes (implied in Spider-Man: No Way Home)]
  • A. hasLimitedMagic
    Indicates that an entity possesses magical abilities that are restricted in scope, power, frequency, or conditions of use.
  • B. hasAccessToMagic
    Indicates that one entity is able to use, interact with, or benefit from magical powers, resources, or abilities associated with another entity or source.
  • C. hasMagicItem
    Indicates that an entity possesses or is associated with a magical item.
  • D. usesMagic
    Indicates that an entity performs actions or achieves effects by employing magical powers or supernatural abilities.
  • E. usesMagicFor
    Indicates that one entity employs or applies magic as a means to achieve, affect, or perform something involving another entity or context.
  • 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_69f3490209c881908ec0241476715f15 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_6a0079e152648190a9da2add94fc1831 completed May 10, 2026, 12:28 p.m.
PD Predicate disambiguation batch_6a0078f77f9c8190af357a6016a2bd53 completed May 10, 2026, 12:24 p.m.
PDg Predicate description generation batch_6a0079e0a9688190a420759fafd47807 completed May 10, 2026, 12:28 p.m.
Created at: May 1, 2026, 12:28 a.m.