Triple
T3983633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UK Singles Chart |
E86817
|
entity |
| Predicate | chartWeekDefinition |
P42651
|
FINISHED |
| Object | Friday to Thursday |
—
|
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: Friday to Thursday | Statement: [UK Singles Chart, chartWeekDefinition, Friday to Thursday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chartWeekDefinition Context triple: [UK Singles Chart, chartWeekDefinition, Friday to Thursday]
-
A.
trackingWeekEnd
Indicates the point in time marking when a specified tracking period or tracking week concludes.
-
B.
hasWeekLength
Indicates the duration of a week associated with an entity, typically expressed as a number of days.
-
C.
weekEndDay
Indicates that a given day falls on a weekend rather than a weekday.
-
D.
hasWeeklyHolyDay
Indicates that an entity observes or is associated with a recurring holy or sacred day that occurs weekly.
-
E.
timeCharacteristic
chosen
Indicates a relationship where one entity specifies a temporal property, feature, or constraint that characterizes another entity or event.
- 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_69aed93fd9d4819085d3b2137d2346cb |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa3ef7ac8190abe02f440ff83c43 |
completed | March 9, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69aef8f492ac819089dbb9436dbcdd2b |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.