Triple
T13070250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1954 World Series over-the-shoulder catch often called "The Catch" |
E329436
|
entity |
| Predicate | scoreAtTime |
P70624
|
FINISHED |
| Object | 2–2 |
—
|
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: 2–2 | Statement: [1954 World Series over-the-shoulder catch often called "The Catch", scoreAtTime, 2–2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoreAtTime Context triple: [1954 World Series over-the-shoulder catch often called "The Catch", scoreAtTime, 2–2]
-
A.
scoresWhen
chosen
Indicates that one entity achieves a score or points at the time or under the condition specified by another entity or event.
-
B.
decidingScoreTime
Indicates the point in time at which a decisive or game-determining score occurs.
-
C.
scoreScale
Indicates the scale or range on which a score or rating is expressed or measured.
-
D.
endTimePosition
Indicates the temporal position or point in time at which an event, state, or interval comes to an end.
-
E.
timeScaleRank
Indicates the relative position or priority of a time scale compared to other time scales in a ranked ordering.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d980ee6130819095d835e7ff6a8c5b |
completed | April 10, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9 p.m.