Triple
T14905545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2010 Rose Bowl Game |
E360119
|
entity |
| Predicate | ohioStateRecordEnteringGame |
P116619
|
FINISHED |
| Object | 10–2 |
—
|
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–2 | Statement: [2010 Rose Bowl Game, ohioStateRecordEnteringGame, 10–2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ohioStateRecordEnteringGame Context triple: [2010 Rose Bowl Game, ohioStateRecordEnteringGame, 10–2]
-
A.
cityOhioStateHomeGames
Indicates that a city in Ohio is the location where a team plays its home games.
-
B.
OregonRecordEnteringGame
Indicates that a team or player is entering a game holding a record specific to Oregon (such as a state, school, or program record) at that time.
-
C.
oregonStateRankingEnteringGame
Indicates the competitive ranking position held by Oregon State at the time the game began.
-
D.
ClevelandBrownsRecordEnteringGame
Indicates the win-loss (and possibly tie) record that the Cleveland Browns had prior to a specific game.
-
E.
ChiefsRecordEnteringGame
Indicates the win-loss (and possibly tie) record the Chiefs had prior to the start of a specific game.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded60cd5588190b1efecc2b220da69 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:12 a.m.