Triple
T28374968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aladdin – A Musical Spectacular |
E718731
|
entity |
| Predicate | replacementShow |
P180139
|
FINISHED |
| Object | Frozen – Live at the Hyperion |
—
|
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: Frozen – Live at the Hyperion | Statement: [Aladdin – A Musical Spectacular, replacementShow, Frozen – Live at the Hyperion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacementShow Context triple: [Aladdin – A Musical Spectacular, replacementShow, Frozen – Live at the Hyperion]
-
A.
replacement
Indicates that one entity takes the place of, or is substituted for, another entity in a given context.
-
B.
replacementName
Indicates that one entity serves as a substitute or successor name for another entity, effectively replacing the original designation.
-
C.
replacementProject
Indicates that one entity is a project intended to replace or supersede another entity or project.
-
D.
replacementMember
Indicates that one entity serves as a substitute or successor taking over the role, position, or function previously held by another entity.
-
E.
replacementOutcome
Indicates the result or consequence that follows from one entity being replaced by another.
- F. None of above. chosen
Provenance (4 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
| PDg | Predicate description generation | batch_69f73221eef88190bd8905e6e9f5a586 |
completed | May 3, 2026, 11:31 a.m. |
Created at: April 28, 2026, 1:02 a.m.