Triple
T3464449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2020 Oregon–Oregon State football game |
E73101
|
entity |
| Predicate | awayTeamRanked |
P2621
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [2020 Oregon–Oregon State football game, awayTeamRanked, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awayTeamRanked Context triple: [2020 Oregon–Oregon State football game, awayTeamRanked, true]
-
A.
awayTeam
chosen
Indicates that an entity is designated as the visiting or non-home team in a competitive event or match.
-
B.
awayTeamRegularSeasonPosition
Indicates the final standing or rank that the away team achieved in the regular season.
-
C.
homeTeam
Indicates that one entity is designated as the home team in a game, match, or sporting event involving another entity.
-
D.
managerAwayTeam
Indicates that a person serves as the manager (coach/head coach) of the away team in a given match or event.
-
E.
otherDominantTeam
Indicates that one team is recognized as the primary or stronger team in contrast to another team that is considered the other dominant side in a given context or competition.
- 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb0dc100819084bb0c355c7bb15b |
completed | March 8, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.