Triple
T36605569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Fairytale Hall |
E903034
|
entity |
| Predicate | hasMeetConfiguration |
P13644
|
FINISHED |
| Object | two separate princess meet-and-greet queues |
—
|
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: two separate princess meet-and-greet queues | Statement: [Princess Fairytale Hall, hasMeetConfiguration, two separate princess meet-and-greet queues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeetConfiguration Context triple: [Princess Fairytale Hall, hasMeetConfiguration, two separate princess meet-and-greet queues]
-
A.
hasConfiguration
chosen
Indicates that an entity is associated with or defined by a particular configuration or setup.
-
B.
hasMet
Indicates that one entity has encountered or come into contact with another entity at least once.
-
C.
mustMeet
Indicates that one entity is required or obligated to have a meeting or encounter with another entity.
-
D.
hasGradeConfiguration
Indicates that an entity is associated with a specific setup or scheme defining how grades are structured, calculated, or applied.
-
E.
hasSafetyConfiguration
Indicates that an entity is associated with or assigned a particular safety-related setup, parameters, or protective settings.
- 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_69ff6a4ce9a08190b98abde3a170dd69 |
completed | May 9, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69ff69c11634819089d1084bd2c11534 |
completed | May 9, 2026, 5:07 p.m. |
Created at: May 3, 2026, 4:11 p.m.