Triple
T36231361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1978 Major League Baseball season |
E891252
|
entity |
| Predicate | tieBreakerDate |
P58423
|
FINISHED |
| Object | 1978-10-02 |
—
|
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: 1978-10-02 | Statement: [1978 Major League Baseball season, tieBreakerDate, 1978-10-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tieBreakerDate Context triple: [1978 Major League Baseball season, tieBreakerDate, 1978-10-02]
-
A.
tieBreakPlayed
Indicates that a tiebreak game or set was played to resolve a tie in the match or set score.
-
B.
tieBreakerAppointedBy
Indicates that a specific party or authority is responsible for appointing the individual or entity who will act as the tie-breaker in a decision-making process.
-
C.
tieBreakerVenue
Indicates the venue or location that is used to resolve a tie between entities when primary criteria do not produce a winner.
-
D.
tieBreakerMetric
Indicates a metric used to resolve ties when primary comparison criteria result in equal values.
-
E.
tiebreakerGameDate
chosen
Indicates the date on which a tiebreaker game is played or scheduled to occur.
- 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.