Triple
T34981150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Oneders |
E1008816
|
entity |
| Predicate | notableFictionalSong |
P56230
|
FINISHED |
| Object | That Thing You Do! |
E62652
|
NE 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: That Thing You Do! | Statement: [The Oneders, notableFictionalSong, That Thing You Do!]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFictionalSong Context triple: [The Oneders, notableFictionalSong, That Thing You Do!]
-
A.
hasFictionalSong
chosen
Indicates that one entity includes, features, or is associated with a song that is fictional or exists only within a narrative context.
-
B.
notableSongWrittenFor
Indicates that a particular song was specifically written for a given person, group, work, event, or purpose.
-
C.
notableSongInMusical
Indicates that a particular song is especially prominent, well-known, or significant within a given musical.
-
D.
isFictionalSong
Indicates that the referenced song exists only in fiction (e.g., within a story, film, game, or other fictional context) and not as a real-world musical work.
-
E.
notableSongbook
Indicates that there is a notable or significant songbook associated with the given entity.
- F. None of above.
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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37fafeed9c8190b792c64e372f4a62 |
completed | June 21, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.