Triple
T14905553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2010 Rose Bowl Game |
E360119
|
entity |
| Predicate | BCSGame |
P116620
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [2010 Rose Bowl Game, BCSGame, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BCSGame Context triple: [2010 Rose Bowl Game, BCSGame, yes]
-
A.
gameCode
Indicates a code or identifier assigned to a specific game instance or type.
-
B.
typicalGame
Indicates a relationship where one entity is characterized as a standard, representative, or commonly occurring example of a game for the other entity or context.
-
C.
stateGame6
Indicates that an entity is in the specific condition or configuration labeled as "game6" within a set of game-related states.
-
D.
gameEngine
Indicates that one entity serves as the game engine or core runtime system used to develop, run, or power another entity (such as a game or interactive application).
-
E.
gameContext
Indicates the situational framework or environment in which a game’s actions, rules, and interactions take place.
- 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.