Triple
T593828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1907 World Series |
E17334
|
entity |
| Predicate | hasTieGame |
P16052
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [1907 World Series, hasTieGame, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTieGame Context triple: [1907 World Series, hasTieGame, true]
-
A.
seriesWinningGame
Indicates that a particular game is the decisive or clinching game in which one side wins the overall series.
-
B.
hasHistoricalTieTo
Indicates a relationship where one entity is historically connected or linked to another through past events, associations, or influences.
-
C.
isRematchOfFinal
Indicates that a match is a subsequent encounter replaying the same opponents and stakes as a previous final match.
-
D.
hasInterconferenceGame
Indicates that there exists a game played between teams belonging to different conferences.
-
E.
tiebreaker
Indicates that one entity serves as the deciding factor used to break a tie between two or more otherwise equal options or outcomes.
- F. None of above. chosen
Provenance (4 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bd15c5881909b59ed4c88687e7b |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cd7d3c8190af008acf34a2293b |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985ada988190aaea628a9b55bca4 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:33 p.m.