Triple
T14449987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2020 Pac-12 Conference football season |
E358304
|
entity |
| Predicate | scheduleFormat |
P11168
|
FINISHED |
| Object | conference-only schedule |
—
|
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: conference-only schedule | Statement: [2020 Pac-12 Conference football season, scheduleFormat, conference-only schedule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scheduleFormat Context triple: [2020 Pac-12 Conference football season, scheduleFormat, conference-only schedule]
-
A.
schedule
Indicates that an entity arranges for an event, task, or activity to occur at a specific time or within a defined time frame.
-
B.
usesScheduleFormat
chosen
Indicates that one entity adopts or follows the schedule structure, pattern, or formatting defined by another entity.
-
C.
scheduleUS
Indicates that an entity arranges or assigns a time for something specifically within the context of the United States.
-
D.
scheduleUsage
Indicates how and when a schedule is applied or utilized in relation to associated entities or events.
-
E.
scheduledDuring
Indicates that one event or activity is planned to occur within the time interval defined by another event or period.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de916139888190be219678e29a2a3a |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.