Triple
T33405623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patricia (daughter) |
E855429
|
entity |
| Predicate | appearsAcrossScenes |
P795
|
FINISHED |
| Object | multiple eras of the Carousel of Progress show |
—
|
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: multiple eras of the Carousel of Progress show | Statement: [Patricia (daughter), appearsAcrossScenes, multiple eras of the Carousel of Progress show]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsAcrossScenes Context triple: [Patricia (daughter), appearsAcrossScenes, multiple eras of the Carousel of Progress show]
-
A.
performedInScene
Indicates that an action or event took place within a specific scene or setting.
-
B.
appearsIn
chosen
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
C.
appearsInCutscenes
Indicates that the entity is featured or shown within one or more cutscene sequences.
-
D.
appearsFor
Indicates that one entity is presented, shown, or made visible on behalf of, or in representation of, another entity.
-
E.
appearsInContinuity
Indicates that an entity is part of, or occurs within, a specific narrative continuity or canon timeline.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: May 1, 2026, 1:36 a.m.