Triple
T4481448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1962 AFL Championship |
E100142
|
entity |
| Predicate | homeTeamRegularSeasonRecord |
P34055
|
FINISHED |
| Object | 11–3 |
—
|
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: 11–3 | Statement: [1962 AFL Championship, homeTeamRegularSeasonRecord, 11–3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeTeamRegularSeasonRecord Context triple: [1962 AFL Championship, homeTeamRegularSeasonRecord, 11–3]
-
A.
NLTeamRegularSeasonRecord
Indicates the win–loss (and often tie) performance record of a National League baseball team over a regular season.
-
B.
homeTeamRegularSeasonPosition
Indicates the final standing or rank that the home team achieved in the regular season within its league or competition.
-
C.
homeTeamRecordEnteringGame
chosen
Indicates the win-loss (and possibly tie) record that the home team had prior to the start of the game.
-
D.
seasonRecord
Indicates the overall performance or results an entity achieved over the course of a specific season (e.g., wins, losses, or comparable outcome metrics).
-
E.
ALTeamRegularSeasonRecord
Indicates the relationship that specifies a team's win–loss record during the American League regular 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_69b34553cbe48190afa8ac1cac285b86 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35728ed508190ba0e882fa62d8848 |
completed | March 13, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69b3563d63008190816e37027e761375 |
completed | March 13, 2026, 12:11 a.m. |
Created at: March 12, 2026, 11:36 p.m.