Triple
T6253353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1984-06-23 "The Sandberg Game" vs St. Louis Cardinals |
E140099
|
entity |
| Predicate | innings |
P69729
|
FINISHED |
| Object | 11 |
—
|
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: 11 | Statement: [1984-06-23 "The Sandberg Game" vs St. Louis Cardinals, innings, 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: innings Context triple: [1984-06-23 "The Sandberg Game" vs St. Louis Cardinals, innings, 11]
-
A.
inningsPitched
Indicates the number of innings a pitcher has completed while actively pitching in a game or season.
-
B.
underlies
Indicates that one entity serves as a fundamental basis, support, or underlying cause for another entity, condition, or phenomenon.
-
C.
underpins
Indicates that one entity serves as the fundamental basis, support, or justification for another.
-
D.
liesBeyond
Indicates that one entity is located at a greater distance or outside the boundary of another reference point, region, or limit.
-
E.
secretes
Indicates that one entity produces and releases a substance from within itself into its surrounding environment or another entity.
- 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_69c008b4858c819095b0199114a9a87b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063417c8c8190945049881819d307 |
completed | March 22, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c05707d5408190a1d0fd80414ad957 |
completed | March 22, 2026, 8:54 p.m. |
Created at: March 22, 2026, 4:24 p.m.