Triple
T269386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Billboard Hot 100 |
E5595
|
entity |
| Predicate | chartIssueDate |
P6878
|
FINISHED |
| Object | Saturday (historical) |
—
|
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: Saturday (historical) | Statement: [U.S. Billboard Hot 100, chartIssueDate, Saturday (historical)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chartIssueDate Context triple: [U.S. Billboard Hot 100, chartIssueDate, Saturday (historical)]
-
A.
dateOf
chosen
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
B.
date
Indicates that two entities are engaged in or participate in a romantic or social outing or relationship with each other.
-
C.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
-
D.
datePresented
Indicates the date on which something (such as an item, work, or information) was formally presented or made known to an audience or recipient.
-
E.
integrationDate
Indicates the date on which two or more entities, systems, or components are combined or brought into a unified whole.
- 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_69a25853594c8190b05ec3a586ec88bf |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25db00ed48190be6f598807265356 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b70d99c819085d8381a313a2a34 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:57 a.m.