Triple
T13801144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NL |
E331641
|
entity |
| Predicate | hasRegularSeasonSchedule |
P8333
|
FINISHED |
| Object | home-and-away 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: home-and-away games | Statement: [NL, hasRegularSeasonSchedule, home-and-away games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegularSeasonSchedule Context triple: [NL, hasRegularSeasonSchedule, home-and-away games]
-
A.
hasRegularSeason
Indicates that an entity (such as a league, competition, or sport) includes or is associated with a defined regular season phase of play.
-
B.
hasRegularSeasonCoverage
Indicates that an entity provides media or broadcast coverage of another entity’s regular season events or games.
-
C.
includesRegularSeasonOnly
Indicates that the referenced data or statistics are restricted to regular season events and exclude postseason or other non-regular-season games.
-
D.
hasRegularSeasonMeetings
Indicates that one entity holds recurring scheduled meetings with another entity during the regular season.
-
E.
seasonSchedule
chosen
Indicates the planned timing and sequence of events, activities, or occurrences within 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de025ded6c8190851c108ae559a355 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.