Triple
T31976285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Point of Grace |
E816456
|
entity |
| Predicate | hasBillboardNumberOneSingles |
P178088
|
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: [Point of Grace, hasBillboardNumberOneSingles, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBillboardNumberOneSingles Context triple: [Point of Grace, hasBillboardNumberOneSingles, 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.
numberOfUSNumberOneSingles
Indicates the count of times an entity has achieved a number-one single on the official United States music charts.
-
C.
hasBillboardCountryNumberOneSingle
Indicates that an entity has achieved at least one single that reached number one on the Billboard Country music charts.
-
D.
hasBillboard200NumberOne
Indicates that an entity (typically an album or song) has reached the number one position on the Billboard 200 chart.
-
E.
numberOfWeeksAtNumberOne
Indicates the duration, measured in weeks, that something remained in the number-one position.
- 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f707f380388190954b79d52a321921 |
completed | May 3, 2026, 8:31 a.m. |
Created at: May 1, 2026, 12:11 a.m.