Triple
T4996371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2007 College World Series |
E112255
|
entity |
| Predicate | finalGameScoreGame2 |
P52765
|
FINISHED |
| Object | Oregon State 9–3 North Carolina |
—
|
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: Oregon State 9–3 North Carolina | Statement: [2007 College World Series, finalGameScoreGame2, Oregon State 9–3 North Carolina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalGameScoreGame2 Context triple: [2007 College World Series, finalGameScoreGame2, Oregon State 9–3 North Carolina]
-
A.
game6FinalScore
Indicates the final score achieved in the sixth game of a series or sequence of games.
-
B.
finalSecondLegScore
chosen
Indicates the score achieved in the second leg of a two-leg competition or matchup once that leg is completed.
-
C.
game7Score
Indicates the final score or outcome of a decisive seventh game in a series between competitors.
-
D.
opponentFinalScore
Indicates the final score achieved by an opposing participant or team in a contest or game.
-
E.
finalHomeGameResult
Indicates the outcome of an entity’s last home game in a given context or season.
- 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_69bd4432b32c81909f3b3c6bd10f0653 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7472a1dc8190942f568a81fdd961 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd714aee2481908fb0dd5fa2daf3a1 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:34 p.m.