Triple
T18951795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1968 AFL Championship Game |
E463671
|
entity |
| Predicate | raiderPointsByQuarterPattern |
P30630
|
FINISHED |
| Object | close, competitive scoring throughout |
—
|
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: close, competitive scoring throughout | Statement: [1968 AFL Championship Game, raiderPointsByQuarterPattern, close, competitive scoring throughout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raiderPointsByQuarterPattern Context triple: [1968 AFL Championship Game, raiderPointsByQuarterPattern, close, competitive scoring throughout]
-
A.
RavensPointsByQuarter
Indicates the number of points the Ravens scored in each quarter of a game.
-
B.
awayTeamPointsByQuarter
Indicates the number of points scored by the away team in each quarter of a game.
-
C.
scoringSummaryFourthQuarter
Indicates the scoring events or point totals that occurred during the fourth quarter of a game.
-
D.
GiantsPointsByQuarter
Indicates the number of points the Giants scored in each quarter of a game.
-
E.
quarterScores
chosen
Indicates the scores achieved in each quarter of a game, match, or period-based 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d54385e08190903a054681352d11 |
completed | April 20, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon