Triple
T15309359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Division (Sun Belt Conference football) |
E365986
|
entity |
| Predicate | influencesScheduling |
P26550
|
FINISHED |
| Object | cross-division games |
—
|
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: cross-division games | Statement: [East Division (Sun Belt Conference football), influencesScheduling, cross-division games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influencesScheduling Context triple: [East Division (Sun Belt Conference football), influencesScheduling, cross-division games]
-
A.
effectOnSchedule
chosen
Indicates how an event, action, or condition changes, disrupts, or influences a planned schedule or timeline.
-
B.
notableSchedulingFact
Indicates that there is a noteworthy or unusual fact about how an event, activity, or process is scheduled or timed.
-
C.
scheduledDuring
Indicates that one event or activity is planned to occur within the time interval defined by another event or period.
-
D.
schedulingRule
Indicates a rule or constraint that governs when, how, or under what conditions an event or task may be scheduled.
-
E.
schedule
Indicates that an entity arranges for an event, task, or activity to occur at a specific time or within a defined time frame.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03cd176708190b0f6ba17aed92f8e |
completed | April 16, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:16 a.m.