Triple
T10479872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2020 National League Championship Series |
E247141
|
entity |
| Predicate | hostBallparkOpened |
P2965
|
FINISHED |
| Object | 2020 |
—
|
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: 2020 | Statement: [2020 National League Championship Series, hostBallparkOpened, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostBallparkOpened Context triple: [2020 National League Championship Series, hostBallparkOpened, 2020]
-
A.
hasBallpark
Indicates that an entity possesses, is associated with, or includes a specific ballpark as part of its attributes or facilities.
-
B.
ballparkOpeningYear
chosen
Indicates the calendar year in which a ballpark first officially opened for use.
-
C.
firstHostBallpark
Indicates the ballpark where a team or player first hosted a game or event.
-
D.
managedHomeBallpark
Indicates that one entity served as the manager of a sports team while that team was based at or associated with a particular home ballpark.
-
E.
homeBallparkCapacityApprox
Indicates that the relationship specifies an approximate seating capacity of a team's home ballpark.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5095b2ec881909e1220d83e750a75 |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8a30848190b33cf43f005a028e |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:22 p.m.