Triple
T763487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFC North |
E16121
|
entity |
| Predicate | hasSeasonFormat |
P2147
|
FINISHED |
| Object | home-and-away games within division |
—
|
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: home-and-away games within division | Statement: [NFC North, hasSeasonFormat, home-and-away games within division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeasonFormat Context triple: [NFC North, hasSeasonFormat, home-and-away games within division]
-
A.
hasSeason
Indicates that an entity possesses, occurs during, or is associated with a particular season or set of seasons.
-
B.
hasSeasonalStatus
Indicates that an entity’s status, availability, or condition varies according to a particular season or time of year.
-
C.
hasSeasonalPattern
Indicates that the occurrence, intensity, or characteristics of something regularly vary according to a recurring seasonal cycle.
-
D.
seasonStructure
chosen
Indicates how a season is organized or structured in terms of its component parts, phases, or format.
-
E.
expandedFormatFromSeason
Indicates that one entity is an expanded or extended version of another entity that originates from a specific season.
- 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a69c8c448190a036a04fd8fdd2c2 |
completed | March 1, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69a4a506106081909ef97a679ff00a5a |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.