Triple

T36604577
Position Surface form Disambiguated ID Type / Status
Subject China Pavilion at EPCOT E903012 entity
Predicate characterMeetAndGreet P30896 FINISHED
Object Mulan 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: Mulan | Statement: [China Pavilion at EPCOT, characterMeetAndGreet, Mulan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: characterMeetAndGreet
Context triple: [China Pavilion at EPCOT, characterMeetAndGreet, Mulan]
  • A. featuresCharacterMeetAndGreets chosen
    Indicates that the subject offers opportunities for visitors to meet and interact with characters in organized meet-and-greet sessions.
  • B. encountersCharacter
    Indicates that one character comes into contact with or meets another character, typically within a particular situation or context.
  • C. meetsAs
    Indicates that two entities encounter or come together at the same place and time, typically in a planned or recognized interaction.
  • D. hasIndoorMeetAndGreet
    Indicates that an entity offers an indoor location where visitors can meet and interact with a specified character or representative.
  • E. meetsVia
    Indicates that two entities come into contact or interact with each other through a specified intermediary medium, channel, or mechanism.
  • 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_69f76e66b7b88190848f7a3e1188915f completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69ffbe9e47688190a2692566dc326646 completed May 9, 2026, 11:09 p.m.
PD Predicate disambiguation batch_69ffbb7b45388190b62cbde5c2d435cd completed May 9, 2026, 10:55 p.m.
Created at: May 3, 2026, 4:11 p.m.