Triple
T784039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFC South |
E16560
|
entity |
| Predicate | schedulingFormat |
P11168
|
FINISHED |
| Object | each team plays division opponents twice per season |
—
|
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: each team plays division opponents twice per season | Statement: [NFC South, schedulingFormat, each team plays division opponents twice per season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schedulingFormat Context triple: [NFC South, schedulingFormat, each team plays division opponents twice per season]
-
A.
usesScheduleFormat
chosen
Indicates that one entity adopts or follows the schedule structure, pattern, or formatting defined by another entity.
-
B.
schedule
Indicates that an entity arranges for an event, task, or activity to occur at a specific time or within a defined time frame.
-
C.
typicalSchedule
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
-
D.
format
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
E.
competitionFormat
Indicates the specific structure or ruleset under which a competition is organized and conducted.
- 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_69a4936ad1fc81908f190208059ccf78 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a769dc6481908f12e872f997acf3 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a50db97c8190a1c55673f4a357b4 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.