Triple
T332355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephen Strasburg |
E6651
|
entity |
| Predicate | hasStatCategory |
P3976
|
FINISHED |
| Object | strikeouts |
—
|
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: strikeouts | Statement: [Stephen Strasburg, hasStatCategory, strikeouts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStatCategory Context triple: [Stephen Strasburg, hasStatCategory, strikeouts]
-
A.
hasStatisticalLeaderCategory
Indicates that an entity is associated with a specific category under which it is recognized as a statistical leader (e.g., in performance metrics or records).
-
B.
hasStatistics
chosen
Indicates that an entity is associated with one or more statistical measures, records, or summaries describing its quantitative properties or performance.
-
C.
hasMajorCategory
Indicates that something is associated with or classified under a primary, overarching category.
-
D.
hasNumberCategory
Indicates that an entity is associated with a specific numerical classification or type.
-
E.
hasMarketingCategory
Indicates that an entity is associated with a specific marketing category or segment used for classification or targeting.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eab1a7048190ac690ddc2e294914 |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94c6d8881908239d3788c018adf |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.