Triple
T559815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFC West |
E13423
|
entity |
| Predicate | usesSchedulingFormat |
P11168
|
FINISHED |
| Object | NFL divisional scheduling |
—
|
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: NFL divisional scheduling | Statement: [AFC West, usesSchedulingFormat, NFL divisional scheduling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSchedulingFormat Context triple: [AFC West, usesSchedulingFormat, NFL divisional scheduling]
-
A.
usesScheduleFormat
chosen
Indicates that one entity adopts or follows the schedule structure, pattern, or formatting defined by another entity.
-
B.
containsSchedule
Indicates that one entity includes or holds a schedule associated with another entity or activity.
-
C.
usesClockSystem
Indicates that one entity employs or operates according to the clock or timekeeping system defined or provided by another entity.
-
D.
usesStandard
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
-
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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a499e13694819087a236bffa6601a9 |
completed | March 1, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69a494befb8481908bb4e2e9f31e343b |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.