Triple
T34304114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Football League All-Star Game |
E880261
|
entity |
| Predicate | playedAfterSeason |
P6586
|
FINISHED |
| Object | AFL 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: AFL season | Statement: [American Football League All-Star Game, playedAfterSeason, AFL season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedAfterSeason Context triple: [American Football League All-Star Game, playedAfterSeason, AFL season]
-
A.
playedThroughSeason
Indicates that an entity (typically a player) participated continuously for the duration of a specified season.
-
B.
playedFromSeason
Indicates the starting season from which an entity (such as a player or participant) began playing for or being active with another entity (such as a team or organization).
-
C.
playedAfter
chosen
Indicates that one event, performance, or action occurred later in time than another.
-
D.
playedInSeason
Indicates that an entity (such as a player or participant) took part in or was active during a specific season.
-
E.
playsInSeason
Indicates that an entity participates or performs in a specific season of an ongoing series, competition, or event.
- 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_69f349b79f6c81909cb468c92c39c74d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 1, 2026, 1:57 a.m.