Triple
T3008196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pac-12 college football (selected games) |
E81952
|
entity |
| Predicate | typicalBroadcastDays |
P14563
|
FINISHED |
| Object | 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: Thursday | Statement: [Pac-12 college football (selected games), typicalBroadcastDays, Thursday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBroadcastDays Context triple: [Pac-12 college football (selected games), typicalBroadcastDays, Thursday]
-
A.
broadcastDay
chosen
Indicates the specific day on which a program, event, or content is broadcast or scheduled to be broadcast.
-
B.
typicalBroadcastMonth
Indicates the month in which something is most commonly or characteristically broadcast.
-
C.
broadcastNetworkTypical
Indicates that a given broadcast network is the one typically or commonly associated with airing the specified content or program.
-
D.
typicalBroadcastFormat
Indicates the usual or standard broadcast format in which something (such as a program or content) is typically transmitted.
-
E.
typicalSchedule
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
- 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_69ad8b1c4de88190a83b7cefaa1f2842 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a4ba6988190be29c00cd4266941 |
completed | March 8, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69ad96180eb08190a524c5f458d41382 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.