Triple
T25541824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woman |
E640192
|
entity |
| Predicate | notableLyricCharacteristic |
P140745
|
FINISHED |
| Object | empowering lyrics |
—
|
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: empowering lyrics | Statement: [Woman, notableLyricCharacteristic, empowering lyrics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLyricCharacteristic Context triple: [Woman, notableLyricCharacteristic, empowering lyrics]
-
A.
notableSongCharacteristic
Indicates that a song is distinguished by a particular notable feature or quality, such as style, structure, or performance trait.
-
B.
lyricCharacterization
chosen
Indicates how the lyrics portray, describe, or characterize a subject within a song or musical work.
-
C.
notableLyricReference
Indicates that one entity contains a significant or well-known reference to the lyrics of another entity (such as a song or musical work).
-
D.
notableChorus
Indicates that an entity is recognized for having a particularly prominent or distinguished chorus section.
-
E.
notableSoundCharacteristic
Indicates a distinctive or noteworthy quality of the sound produced or associated with an 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: April 21, 2026, 3:26 p.m.