Triple
T1863835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 90125 |
E34874
|
entity |
| Predicate | Owner of a Lonely Heart_chartPosition_USBillboardHot100 |
P9942
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [90125, Owner of a Lonely Heart_chartPosition_USBillboardHot100, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Owner of a Lonely Heart_chartPosition_USBillboardHot100 Context triple: [90125, Owner of a Lonely Heart_chartPosition_USBillboardHot100, 1]
-
A.
weeksAtNumberOneUSBillboardHot100
Indicates the number of weeks a song or recording remained at the #1 position on the US Billboard Hot 100 chart.
-
B.
ownerOfSomeTrack
chosen
Indicates that an entity has ownership of at least one track (such as a song, audio track, or similar item).
-
C.
notableMistress
Indicates that a person is notably recognized as the mistress (non-marital romantic partner) of another person.
-
D.
hasSong
Indicates that one entity possesses, features, or includes a particular song.
-
E.
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.
- 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_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. |
Created at: March 4, 2026, 7:34 p.m.