Triple
T13661070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Puffy Shirt |
E326993
|
entity |
| Predicate | networkTimeslot |
P14564
|
FINISHED |
| Object | Thursday night |
—
|
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: Thursday night | Statement: [The Puffy Shirt, networkTimeslot, Thursday night]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkTimeslot Context triple: [The Puffy Shirt, networkTimeslot, Thursday night]
-
A.
broadcastTimeSlot
chosen
Indicates the specific time period during which a broadcast (such as a TV or radio program) is scheduled to air.
-
B.
timeSlotOfWorks
Indicates the specific time period or interval during which the works (e.g., tasks, events, or activities) are scheduled or take place.
-
C.
timeTabledBy
Indicates that an event or activity has been scheduled or placed on a timetable by a particular agent or organizing entity.
-
D.
laterRunTimeSlotNetwork
Indicates that one time slot for running a network-related task occurs later than another comparable time slot.
-
E.
typicalTimes
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc620df208190afaccf3ddd10aa60 |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:52 p.m.