Triple
T10099292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1920 World Series |
E215955
|
entity |
| Predicate | gameWithMultipleHistoricPlays |
P85405
|
FINISHED |
| Object | Game 5 |
—
|
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: Game 5 | Statement: [1920 World Series, gameWithMultipleHistoricPlays, Game 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameWithMultipleHistoricPlays Context triple: [1920 World Series, gameWithMultipleHistoricPlays, Game 5]
-
A.
gamePlayed
Indicates that a particular game is or was played by an entity (such as a person, team, or group) during a specific event or time.
-
B.
gameNumberInHistory
chosen
Indicates the position or sequence number of a particular game within a larger historical series or record of games.
-
C.
gamesPlayed
Indicates the number or set of games that an entity has participated in or completed.
-
D.
inningsPlayed
Indicates the number of innings in which an entity (typically a player or team) has participated during a game or season.
-
E.
eraPlayed
Indicates the historical or stylistic time period during which something (typically a work or performance) was played or took place.
- 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_69ca83a4947c8190823a7495dc5d96ed |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd07d686481908d9bb91392954474 |
completed | April 2, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:02 p.m.