Triple
T31756143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fireworks at Walt Disney World |
E810559
|
entity |
| Predicate | audioDistributedBy |
P45475
|
FINISHED |
| Object | in-park speaker systems |
—
|
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: in-park speaker systems | Statement: [Fireworks at Walt Disney World, audioDistributedBy, in-park speaker systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioDistributedBy Context triple: [Fireworks at Walt Disney World, audioDistributedBy, in-park speaker systems]
-
A.
hasSpeakerDistribution
Indicates how speakers of a language or dialect are geographically or demographically distributed.
-
B.
distributesFrom
Indicates that something acts as the source or origin from which items, resources, or information are distributed to others.
-
C.
audioMedium
Indicates that something is conveyed, stored, or presented through an audio-based medium or format.
-
D.
distributesIn
Indicates that one entity allocates or hands out something (e.g., items, resources, information) within or across a specified area, group, or context.
-
E.
audibleIn
chosen
Indicates that a sound produced by one entity can be heard within the spatial or contextual range of another entity.
- 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab7cf30c81908c8fd2500c358e83 |
completed | May 3, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:29 p.m.