Triple
T22677281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1963 AFL Championship Game |
E560377
|
entity |
| Predicate | pointsByVisitingTeam |
P149204
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [1963 AFL Championship Game, pointsByVisitingTeam, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointsByVisitingTeam Context triple: [1963 AFL Championship Game, pointsByVisitingTeam, 10]
-
A.
pointsHomeTeam
Indicates the number of points scored or accumulated by the home team in a game or match.
-
B.
visitingTeamRecordEnteringGame
Indicates the performance record (such as wins and losses) that the visiting team has accumulated prior to the start of the game.
-
C.
locationTeam2Home
Indicates that the specified location serves as the home venue or home ground for the second team involved in the context.
-
D.
goalsHomeTeam
Indicates the number of goals scored by the home team in a match.
-
E.
locationTeam1Home
Indicates that the specified location serves as the home venue or home ground for team 1 in the relationship.
- F. None of above. chosen
Provenance (4 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1785d93e48190b37d11642b0cb123 |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:11 p.m.