Triple
T37284467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don Larsen's perfect game |
E925492
|
entity |
| Predicate | completeGame |
P21410
|
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: [Don Larsen's perfect game, completeGame, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completeGame Context triple: [Don Larsen's perfect game, completeGame, true]
-
A.
completeGames
chosen
Indicates that an entity has finished participating in or playing a game from start to end.
-
B.
winnerCompleteGames
Indicates that the subject is the winner in terms of having completed more full (start-to-finish) games than the object.
-
C.
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.
-
D.
gamesEnded
Indicates that one or more games have concluded, reaching their final state or outcome.
-
E.
typicalGame
Indicates a relationship where one entity is characterized as a standard, representative, or commonly occurring example of a game for the other entity or context.
- 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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.