Triple
T34364561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Formula of Love: O+T=<3 |
E881970
|
entity |
| Predicate | hasSubunitSongs |
P200525
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Formula of Love: O+T=<3, hasSubunitSongs, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubunitSongs Context triple: [Formula of Love: O+T=<3, hasSubunitSongs, yes]
-
A.
hasMusicUnit
Indicates that one entity includes, is associated with, or is organized into a specific musical unit (such as a band, ensemble, or musical subgroup).
-
B.
hasSong
Indicates that one entity possesses, features, or includes a particular song.
-
C.
hasSpecialSong
Indicates that one entity possesses or is associated with a particular song that is unique, distinctive, or specially designated for it.
-
D.
sangSongsIn
Indicates that one entity performed or vocalized songs in the context, location, or event associated with another entity.
-
E.
hasSongCycle
Indicates that one entity (typically a musical work or collection) includes or is associated with a specific song cycle as part of its structure or content.
- 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_69f349be5c9c81908dc726ae1f4c68f2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff9361943c81909544203cbc998a69 |
completed | May 9, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69ff913138a08190b59bdc9d8d199eb3 |
completed | May 9, 2026, 7:55 p.m. |
| PDg | Predicate description generation | batch_69ff935f48808190aa6f4834f59d45b8 |
completed | May 9, 2026, 8:04 p.m. |
Created at: May 1, 2026, 1:58 a.m.