Triple
T34588257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pioneer League championships |
E888104
|
entity |
| Predicate | isDecidingSeriesFor |
P179675
|
FINISHED |
| Object | Pioneer League title |
—
|
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: Pioneer League title | Statement: [Pioneer League championships, isDecidingSeriesFor, Pioneer League title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDecidingSeriesFor Context triple: [Pioneer League championships, isDecidingSeriesFor, Pioneer League title]
-
A.
decidingSeriesResult
Indicates that an event or action determines the final outcome of a competitive series between parties.
-
B.
formatOfDecidingSeries
Indicates the specific competition format or structure used to determine the winner in a deciding series.
-
C.
isSeriesOf
Indicates that one entity is a sequence or set of related items that collectively form a series associated with another entity.
-
D.
intendedForSeries
Indicates that something is designed, created, or designated to be used within or as part of a particular series.
-
E.
decidingSeriesLoser
Indicates that one entity is the loser in a game or match that determines the outcome of a series between competitors.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7238172748190b8cd340ad1f4ba80 |
completed | May 3, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f72349f1108190b6a06758ab2f40bb |
completed | May 3, 2026, 10:28 a.m. |
Created at: May 1, 2026, 2:03 a.m.