Triple
T6136911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1969 AFL season |
E136855
|
entity |
| Predicate | regularSeason |
P25200
|
FINISHED |
| Object | 1969 AFL regular 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: 1969 AFL regular season | Statement: [1969 AFL season, regularSeason, 1969 AFL regular season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularSeason Context triple: [1969 AFL season, regularSeason, 1969 AFL regular season]
-
A.
regularSeasonSuccess
Indicates the degree to which an entity achieves positive outcomes or strong performance during the regular season phase of a competition or activity.
-
B.
hasRegularSeason
chosen
Indicates that an entity (such as a league, competition, or sport) includes or is associated with a defined regular season phase of play.
-
C.
regularSeasonStart
Indicates the date or point in time when a competition’s regular season officially begins.
-
D.
regularSeasonTitle
Indicates that a team or competitor won the championship or top standing for the regular season portion of a competition or league.
-
E.
trainingSeason
Indicates the specific season or time period during which training activities or programs take place.
- 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_69c008a179388190a3b5a081bbf46d55 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05c8211d48190bc10675ba6707150 |
completed | March 22, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c055f19b0c81908be34a00ab218723 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:15 p.m.