Triple
T2409442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbus Clippers |
E50351
|
entity |
| Predicate | wonTriple-ATitle |
P12323
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Columbus Clippers, wonTriple-ATitle, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wonTriple-ATitle Context triple: [Columbus Clippers, wonTriple-ATitle, 2010]
-
A.
wonTitleWith
Indicates that an entity secured a specific title, award, or championship while being associated with or representing another entity (such as a team, organization, or group).
-
B.
wonTripleALeagueChampionship
chosen
Indicates that an entity has achieved victory in a Triple-A level baseball league championship.
-
C.
wonTitleFrom
Indicates that one entity obtained a title or championship by defeating or surpassing another specific entity who previously held it.
-
D.
winnerTitle
Indicates the formal title or designation awarded to the entity that wins a particular competition, contest, or event.
-
E.
wonLeagueTitle
Indicates that a team or individual finished a competition as champions, securing the league title for that season or tournament.
- 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_69a88b0339a88190a1207333cd271cc9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abceab9ce881909ae0a2f34515c11e |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5a530e8819094105aa92dfaf6b3 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:58 p.m.