Triple
T13119618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starman |
E311687
|
entity |
| Predicate | hasAudioCue |
P22084
|
FINISHED |
| Object | invincibility theme music |
—
|
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: invincibility theme music | Statement: [Starman, hasAudioCue, invincibility theme music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAudioCue Context triple: [Starman, hasAudioCue, invincibility theme music]
-
A.
hasCue
Indicates that one entity provides, contains, or is associated with a signal or prompt that can guide or trigger another entity’s behavior or response.
-
B.
hasAudioFeature
Indicates that one entity possesses or is associated with a specific audio-related characteristic or property.
-
C.
hasSound
chosen
Indicates that an entity produces, emits, or is associated with a particular sound.
-
D.
usesAudioFrom
Indicates that one entity incorporates or relies on the audio content produced or provided by another entity.
-
E.
auditoryIconOf
Indicates that one entity is an auditory icon that sonically represents, symbolizes, or stands in for another entity or concept.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98196e69081909111407ee3d9f08e |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98043a74c81908648e6cd0b4c7f71 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:06 p.m.