Triple
T7628903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2007 Los Angeles Dodgers season |
E172708
|
entity |
| Predicate | homeOpeningDayDate |
P548
|
FINISHED |
| Object | 2007-04-09 |
—
|
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: 2007-04-09 | Statement: [2007 Los Angeles Dodgers season, homeOpeningDayDate, 2007-04-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeOpeningDayDate Context triple: [2007 Los Angeles Dodgers season, homeOpeningDayDate, 2007-04-09]
-
A.
officialOpeningDate
Indicates the calendar date on which something is formally inaugurated or officially opened for use or operation.
-
B.
homeFieldOpened
chosen
Indicates that a team's designated home field has officially begun operation or been opened for use.
-
C.
openingDateLine16
Indicates the date on which line 16 was officially opened or began operation.
-
D.
officialOpeningYear
Indicates the calendar year in which something was formally opened or inaugurated for official use.
-
E.
expansionOpeningDate
Indicates the date on which an expansion of something (such as a facility, service, or project) was officially opened or became operational.
- 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_69c699517e348190bd3348b6889200f2 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fe73ff7c8190ab1218d97b37416d |
completed | March 27, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e725a88190b1f05dd224f7f4f2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:56 p.m.