Triple
T8039264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World of Sport (ITV wrestling) |
E187394
|
entity |
| Predicate | typicalTimeslot |
P6833
|
FINISHED |
| Object | Saturday afternoon |
—
|
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 afternoon | Statement: [World of Sport (ITV wrestling), typicalTimeslot, Saturday afternoon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTimeslot Context triple: [World of Sport (ITV wrestling), typicalTimeslot, Saturday afternoon]
-
A.
typicalTimes
chosen
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
-
B.
typicalSchedule
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
-
C.
typicalAppointment
Indicates that an appointment represents a standard, usual, or commonly occurring scheduling arrangement between entities.
-
D.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
-
E.
timeSlotOfWorks
Indicates the specific time period or interval during which the works (e.g., tasks, events, or activities) are scheduled or take place.
- 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_69ca82b00cb48190b59a300f70e97bd7 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f1bb1d88190b3d2c83387c8ce43 |
completed | March 31, 2026, 3:27 a.m. |
| PD | Predicate disambiguation | batch_69cb049688208190b32088bd2c5930bc |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:23 p.m.