Triple
T29322564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ben Burtt |
E743551
|
entity |
| Predicate | createdSoundEffectFor |
P47507
|
FINISHED |
| Object | Star Wars franchise |
—
|
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: Star Wars franchise | Statement: [Ben Burtt, createdSoundEffectFor, Star Wars franchise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdSoundEffectFor Context triple: [Ben Burtt, createdSoundEffectFor, Star Wars franchise]
-
A.
soundEffects
chosen
Indicates that one entity produces, contains, or is associated with sound effects used to accompany or enhance another entity.
-
B.
usesSound
Indicates that one entity employs or relies on sound as a means or tool in relation to another entity or context.
-
C.
isSoundProducedBy
Indicates that a particular sound is generated or emitted by a specified source or entity.
-
D.
hasCauseOfSound
Indicates that one entity is the source or origin of a particular sound produced or associated with another entity.
-
E.
soundEngine
Indicates that one entity functions as or provides the sound engine (audio processing or synthesis system) used by 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: April 28, 2026, 1:24 p.m.