Triple
T998062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon State Beavers baseball |
E21539
|
entity |
| Predicate | collegeWorldSeriesTitle |
P5405
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [Oregon State Beavers baseball, collegeWorldSeriesTitle, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collegeWorldSeriesTitle Context triple: [Oregon State Beavers baseball, collegeWorldSeriesTitle, 2006]
-
A.
WorldSeriesTitleWith
Indicates a relationship where two or more entities share a World Series championship title together in the same year or on the same team.
-
B.
worldSeriesTitleYear
chosen
Indicates the year in which a particular World Series title was won.
-
C.
resultingWorldSeries
Indicates the specific World Series event or outcome that results from a given preceding condition, season, or set of circumstances.
-
D.
previousWorldSeries
Indicates that one World Series event immediately precedes another in chronological order.
-
E.
nextWorldSeries
Indicates that one entity is the World Series event that immediately follows another in chronological order.
- 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4e2ad9c81908a0f488d3f261fc3 |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2b057c48190b9e42df9246b3757 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.