Triple
T18146997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fame |
E434414
|
entity |
| Predicate | achievedUSNumberOneSingle |
P27807
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Fame, achievedUSNumberOneSingle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: achievedUSNumberOneSingle Context triple: [Fame, achievedUSNumberOneSingle, true]
-
A.
numberOfUSNumberOneSingles
Indicates the count of times an entity has achieved a number-one single on the official United States music charts.
-
B.
hasBillboardHot100NumberOneSingle
chosen
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.
-
C.
dateReachedNumberOne
Indicates that an entity (such as a song, album, or product) has reached the number one position in a specified ranking or chart.
-
D.
weeksAtNo1Singles
Indicates the number of weeks a given single (song) remained at the number one position on a specified chart.
-
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.
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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de34bb608190a4842e86f2912dec |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.