Triple
T24691802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doosan Bears |
E611457
|
entity |
| Predicate | hasWonPostseasonSeriesIn |
P36149
|
FINISHED |
| Object | KBO League |
—
|
NE NERFINISHED |
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: KBO League | Statement: [Doosan Bears, hasWonPostseasonSeriesIn, KBO League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWonPostseasonSeriesIn Context triple: [Doosan Bears, hasWonPostseasonSeriesIn, KBO League]
-
A.
playedInPostseasonFor
Indicates that an athlete participated in postseason games or competitions as a member of a specified team or organization.
-
B.
notablePostseasonSeries
Indicates that there exists a postseason series in which the subject played a particularly significant or memorable role in relation to the object.
-
C.
postseasonSeriesWinner
chosen
Indicates which competitor or team won a particular postseason series in a sports or competitive context.
-
D.
hasPostseasonHistory
Indicates that an entity has a record of participation or performance in postseason or playoff competitions.
-
E.
madePostseason
Indicates that an individual or team successfully qualified for and participated in the postseason phase of a competition or league.
- 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_69e2c4d678b081908910f4271627a31a |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 3:20 a.m.