Triple

T28127123
Position Surface form Disambiguated ID Type / Status
Subject Avengers Campus (Walt Disney Studios Park) E710957 entity
Predicate hasCharacterEncounter P134166 FINISHED
Object Spider-Man 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: Spider-Man | Statement: [Avengers Campus (Walt Disney Studios Park), hasCharacterEncounter, Spider-Man]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCharacterEncounter
Context triple: [Avengers Campus (Walt Disney Studios Park), hasCharacterEncounter, Spider-Man]
  • A. encountersCharacter
    Indicates that one character comes into contact with or meets another character, typically within a particular situation or context.
  • B. hasEncounter chosen
    Indicates that one entity experiences or comes into contact with another entity or event, typically in a specific context or situation.
  • C. hasNotableTribeAtEncounter
    Indicates that, at the time of the encounter, the entity was associated with or identified as belonging to a notable tribe.
  • D. hasNPC
    Indicates that an entity includes, is associated with, or contains a non-player character (NPC) within its context or structure.
  • E. hasCreature
    Indicates that one entity possesses, contains, or is associated with a particular creature.
  • 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_69ef9b73bd288190a21ae3d6aa14f386 completed April 27, 2026, 5:22 p.m.
NER Named-entity recognition batch_69f7308a096081909d66a56f3c926806 completed May 3, 2026, 11:24 a.m.
PD Predicate disambiguation batch_69f72a00c5f081908b6539d15baf4e12 completed May 3, 2026, 10:57 a.m.
Created at: April 27, 2026, 9:20 p.m.