Triple
T1150369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dominican Summer League |
E23661
|
entity |
| Predicate | gameSchedule |
P8333
|
FINISHED |
| Object | day games primarily |
—
|
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: day games primarily | Statement: [Dominican Summer League, gameSchedule, day games primarily]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameSchedule Context triple: [Dominican Summer League, gameSchedule, day games primarily]
-
A.
seasonSchedule
chosen
Indicates the planned timing and sequence of events, activities, or occurrences within a specific season.
-
B.
game4Date
Indicates the date on which a particular game is scheduled to be played or took place.
-
C.
showSchedule
Indicates that an entity presents or displays a timetable or planned sequence of events for another entity.
-
D.
sportsProgram
Indicates a relationship where an entity is a sports-related program, event, or broadcast organized or provided by another entity.
-
E.
numberOfGamesScheduled
Indicates the total count of games that have been planned or arranged for a given entity or time period.
- 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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bd0bed00819091d71983d787a030 |
completed | March 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4ee3988190ac89c5ae5b10e316 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.