Triple
T30081046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Wanna Go |
E764458
|
entity |
| Predicate | featuresWhistling |
P144957
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [I Wanna Go, featuresWhistling, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresWhistling Context triple: [I Wanna Go, featuresWhistling, true]
-
A.
hasWhistlingHook
Indicates that one entity possesses or is equipped with a specialized hook designed for or characterized by whistling.
-
B.
featuresRiff
Indicates that something includes or prominently showcases a specific musical riff.
-
C.
featuresVocalPercussion
Indicates that the subject includes or makes use of vocal percussion (such as beatboxing or mouth-made rhythmic sounds) as part of its content or performance.
-
D.
notableSoundCharacteristic
chosen
Indicates a distinctive or noteworthy quality of the sound produced or associated with an entity.
-
E.
featuresRichHarmonies
Indicates that the subject contains or employs complex, layered, and sonically dense harmonic structures.
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ffc89596d08190b97bd60b45c7f9c0 |
completed | May 9, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69ffc81ba5dc8190ae94d44e2284948f |
completed | May 9, 2026, 11:49 p.m. |
Created at: April 29, 2026, 7:03 p.m.