Triple
T106738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All of Me |
E2153
|
entity |
| Predicate | lyricalPerspective |
P4917
|
FINISHED |
| Object | first-person love declaration |
—
|
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: first-person love declaration | Statement: [All of Me, lyricalPerspective, first-person love declaration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lyricalPerspective Context triple: [All of Me, lyricalPerspective, first-person love declaration]
-
A.
lyricist
Indicates that one entity is the writer of the words (lyrics) for a musical work associated with another entity.
-
B.
lyricsBy
Indicates that the lyrics of a song or musical work were written or authored by a specified person or entity.
-
C.
artisticStyle
Indicates the artistic movement, style, or aesthetic approach that characterizes how something is created or visually expressed.
-
D.
commonlySungStanzas
Indicates that certain stanzas of a song or poem are those most frequently sung or performed in practice.
-
E.
dramaticForm
Indicates that one entity is expressed, structured, or realized in the form of a particular dramatic genre or theatrical mode.
- F. None of above. chosen
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_69a24e0a5b7c81908d52da08c60dabc4 |
completed | Feb. 28, 2026, 2:08 a.m. |
| NER | Named-entity recognition | batch_69a256ec650c8190bee2067e37065527 |
completed | Feb. 28, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69a2563d33788190999d471b486d5603 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a256ea776081908fec36c3fdfb8d84 |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:12 a.m.