Triple
T17587094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spirits Having Flown |
E428349
|
entity |
| Predicate | numberOfUSNumberOneSingles |
P128114
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Spirits Having Flown, numberOfUSNumberOneSingles, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfUSNumberOneSingles Context triple: [Spirits Having Flown, numberOfUSNumberOneSingles, 3]
-
A.
numberOfTop10SinglesUS
Indicates the number of singles by an entity that have reached the top 10 positions on music charts in the United States.
-
B.
numberOfWeeksAtNumberOne
Indicates the duration, measured in weeks, that something remained in the number-one position.
-
C.
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.
-
D.
weeksAtNumberOneOnBillboardHot100
Indicates the number of weeks a song or recording remained at the #1 position on the Billboard Hot 100 chart.
-
E.
weeksAtNo1Singles
Indicates the number of weeks a given single (song) remained at the number one position on a specified 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e469e41bf08190963848f1597b6e9f |
completed | April 19, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb50b448190a59dd4be33c76db7 |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:51 a.m.