Triple
T31213514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wanna Be Startin’ Somethin’ |
E795810
|
entity |
| Predicate | isEnergetic |
P156256
|
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: [Wanna Be Startin’ Somethin’, isEnergetic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEnergetic Context triple: [Wanna Be Startin’ Somethin’, isEnergetic, true]
-
A.
isVigorous
chosen
Indicates that an entity exhibits strong energy, intensity, or forcefulness in its actions or behavior.
-
B.
hasAggressiveEnergy
Indicates that an entity exhibits or is characterized by intense, forceful, or confrontational energy or behavior toward others.
-
C.
isPlayful
Indicates that an entity tends to engage in lighthearted, fun, or mischievous behavior, often for enjoyment or amusement.
-
D.
isRunEnergyOf
Indicates that a specified value represents the run energy associated with a particular entity or agent.
-
E.
energyLevel
Indicates the amount or intensity of energy possessed, produced, or exhibited by an entity in a given state or context.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c29a76c8190bf35ad938f28c321 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:09 p.m.