Triple
T36605564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Fairytale Hall |
E903034
|
entity |
| Predicate | guestsCanMeet |
P1220
|
FINISHED |
| Object | Cinderella |
—
|
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: Cinderella | Statement: [Princess Fairytale Hall, guestsCanMeet, Cinderella]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guestsCanMeet Context triple: [Princess Fairytale Hall, guestsCanMeet, Cinderella]
-
A.
allowsGuests
Indicates that an entity permits other people, not part of its primary group or membership, to be present or participate.
-
B.
meetsVia
Indicates that two entities come into contact or interact with each other through a specified intermediary medium, channel, or mechanism.
-
C.
meets
chosen
Indicates that two or more entities come together at the same place and time, typically for interaction or a shared purpose.
-
D.
meetsBetween
Indicates that one entity meets or encounters another at some point between two specified reference points or times.
-
E.
meetingsAre
Indicates that certain entities function as or are classified as meetings in relation to one another.
- 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_69f7c33f442c81908300da6a1631180a |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1bbf5848190a698fdbec307886a |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.