Triple

T31445795
Position Surface form Disambiguated ID Type / Status
Subject Cinderella’s Royal Table E802182 entity
Predicate locatedInsideIcon P109650 FINISHED
Object Magic Kingdom park icon Cinderella Castle 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: Magic Kingdom park icon Cinderella Castle | Statement: [Cinderella’s Royal Table, locatedInsideIcon, Magic Kingdom park icon Cinderella Castle]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInsideIcon
Context triple: [Cinderella’s Royal Table, locatedInsideIcon, Magic Kingdom park icon Cinderella Castle]
  • A. locatedInTheInteriorOf chosen
    Indicates that one entity is situated entirely within the inner part or inside area of another entity, rather than on its surface or boundary.
  • B. locatedIn
    Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
  • C. locatedUnder
    Indicates that one entity is positioned directly or generally beneath another entity in space.
  • D. sometimesLocatedIn
    Indicates that an entity is located in a given place only at certain times or under certain conditions, rather than permanently or always.
  • E. likelyLocatedIn
    Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
  • 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_69f348c5a6bc819092a557e95438976f completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_6a019037edbc8190bdaec436ac2fcec6 completed May 11, 2026, 8:15 a.m.
PD Predicate disambiguation batch_6a018fe05a34819080068f588b5ff80c completed May 11, 2026, 8:14 a.m.
Created at: April 30, 2026, 9:09 p.m.