Triple
T36423490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexico national baseball team |
E897225
|
entity |
| Predicate | bestWBCFinishYear |
P155129
|
FINISHED |
| Object | 2023 |
—
|
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: 2023 | Statement: [Mexico national baseball team, bestWBCFinishYear, 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestWBCFinishYear Context triple: [Mexico national baseball team, bestWBCFinishYear, 2023]
-
A.
bestWBCFinish
Indicates the highest (best) finishing position an entity has ever achieved in a World/World-Based Championship event.
-
B.
yearOfBestChampionshipFinish
chosen
Indicates the specific year in which an entity achieved its highest (best) finishing position in a championship competition.
-
C.
mostWinsYears
Indicates the years during which an entity achieved the highest number of wins compared to others or compared to its own performance in other years.
-
D.
yearOfBestOpenFinish
Indicates the year in which an entity achieved its best (highest) finishing position in an Open tournament or championship.
-
E.
yearOfWin
Indicates the specific calendar year in which an entity achieved a particular victory or win.
- 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_69f76e559b10819099d6655a6e14587c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.