Triple
T6666442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeffrey Maier interference play |
E151614
|
entity |
| Predicate | gameResultAfterPlay |
P10213
|
FINISHED |
| Object | game tied |
—
|
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 tied | Statement: [Jeffrey Maier interference play, gameResultAfterPlay, game tied]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameResultAfterPlay Context triple: [Jeffrey Maier interference play, gameResultAfterPlay, game tied]
-
A.
gameOutcome
chosen
Indicates the result or final status of a game, such as which side won, lost, or if it ended in a draw.
-
B.
playerOutcome
Indicates the result or consequence experienced by a player in a game, match, or scenario (such as winning, losing, or drawing).
-
C.
scoreAfterPlay
Indicates the numerical score that results immediately after a specific play or action has been completed.
-
D.
game4Winner
Indicates which participant or side is the winner of the fourth game in a series or match.
-
E.
game3Winner
Indicates that the referenced entity is the winner of the third game in a series or sequence of games.
- 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:02 p.m.