Triple
T355235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 World Series |
E7527
|
entity |
| Predicate | game3Record |
P11626
|
FINISHED |
| Object | longest World Series game by time |
—
|
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: longest World Series game by time | Statement: [2018 World Series, game3Record, longest World Series game by time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: game3Record Context triple: [2018 World Series, game3Record, longest World Series game by time]
-
A.
game3Winner
Indicates that the referenced entity is the winner of the third game in a series or sequence of games.
-
B.
game3Location
Indicates the location or venue where the third game in a series or sequence takes place.
-
C.
game3Venue
Indicates the venue or location where the third game in a series or sequence takes place.
-
D.
game3LosingTeam
Indicates the team that lost in the third game of a series or sequence of games.
-
E.
game3City
Indicates that a game or match (in a series or sequence) takes place in, or is associated with, a particular city.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebad8bf08190b4a38ffd9157d641 |
completed | Feb. 28, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69a2e9589e7c8190b2d3af8f858c96af |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea0b23ec8190bef9d593162388a4 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.