Triple
T14013995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1993 Major League Baseball season |
E337158
|
entity |
| Predicate | sanFranciscoGiantsRecord |
P34045
|
FINISHED |
| Object | 103–59 |
—
|
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: 103–59 | Statement: [1993 Major League Baseball season, sanFranciscoGiantsRecord, 103–59]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sanFranciscoGiantsRecord Context triple: [1993 Major League Baseball season, sanFranciscoGiantsRecord, 103–59]
-
A.
GiantsWorldSeriesOutcome
Indicates the result or status of the San Francisco Giants’ performance in a given World Series.
-
B.
GiantsRegularSeasonRecordEnteringGame
Indicates the Giants’ cumulative regular-season win–loss record at the time a particular game begins.
-
C.
GiantsAndDodgersRecordAfter162Games
Indicates the comparative win–loss records of the Giants and the Dodgers after the completion of a full 162-game regular season.
-
D.
GiantsScore
Indicates that the Giants scored points (such as runs or goals) in a game or event.
-
E.
resultForGiantsSeason
chosen
Indicates the outcome or performance result associated with a specific season of the Giants team.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f37d11481909159bdb9e1e8d38e |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.