Triple
T37359224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porgi, amor |
E927533
|
entity |
| Predicate | lyricAddressee |
P187770
|
FINISHED |
| Object | personified Love |
—
|
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: personified Love | Statement: [Porgi, amor, lyricAddressee, personified Love]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lyricAddressee Context triple: [Porgi, amor, lyricAddressee, personified Love]
-
A.
lyricalCharacter
Indicates that one entity is the character or persona expressed or portrayed in the lyrics of the other entity (such as a song or poem).
-
B.
lyricist
Indicates that one entity is the writer of the words (lyrics) for a musical work associated with another entity.
-
C.
lyricCharacterization
Indicates how the lyrics portray, describe, or characterize a subject within a song or musical work.
-
D.
lyricExpresses
Indicates that the content or emotion of a lyric conveys, communicates, or articulates a particular idea, feeling, or message.
-
E.
hasLyricNarrator
Indicates that a musical or lyrical work is associated with a specific narrator who voices or presents its lyrics.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb8c37931c81909da038c18ed9add2 |
completed | May 6, 2026, 6:45 p.m. |
Created at: May 3, 2026, 4:16 p.m.