Triple
T1863692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Owner of a Lonely Heart |
E34871
|
entity |
| Predicate | isOnlyUSNumberOneSingleFor |
P33221
|
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: [Owner of a Lonely Heart, isOnlyUSNumberOneSingleFor, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnlyUSNumberOneSingleFor Context triple: [Owner of a Lonely Heart, isOnlyUSNumberOneSingleFor, Yes]
-
A.
hasBillboardHot100NumberOneSingle
Indicates that an artist, group, or entity has achieved at least one single that reached the number one position on the Billboard Hot 100 chart.
-
B.
isDebutSingleOf
Indicates that a musical single is the first official release by a particular artist or group.
-
C.
hasSingle
Indicates that an entity possesses exactly one instance of a specified related entity or attribute.
-
D.
singleBy
Indicates that an entity is not in a romantic relationship and is considered single according to a specified criterion or context.
-
E.
weeksAtNumberOneUSBillboardHot100
Indicates the number of weeks a song or recording remained at the #1 position on the US Billboard Hot 100 chart.
- 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_69a88600b2f88190bc09303e68ab517e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abb16c09e48190a345c95eab59fd87 |
completed | March 7, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69abafe02c3c819093a4744b476106ca |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb16a6db48190af04012e8ed2269f |
completed | March 7, 2026, 5:02 a.m. |
Created at: March 4, 2026, 7:34 p.m.