Triple
T30153134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Year of the Pitcher |
E766447
|
entity |
| Predicate | ruleChangeConsequenceFor |
P812
|
FINISHED |
| Object | pitching mound height |
—
|
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: pitching mound height | Statement: [Year of the Pitcher, ruleChangeConsequenceFor, pitching mound height]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruleChangeConsequenceFor Context triple: [Year of the Pitcher, ruleChangeConsequenceFor, pitching mound height]
-
A.
typicalRuleModification
Indicates a change made to a standard or default rule, adjusting how that rule normally applies or operates.
-
B.
ruleInfluence
Indicates that one rule affects, constrains, or modifies the behavior, outcome, or applicability of another rule.
-
C.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
-
D.
hasConsequence
chosen
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
-
E.
consequenceOfInfluence
Indicates that one event, state, or condition occurs as a result of the influence or impact exerted by another.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ed5a87c8190b6d716ef7a34b957 |
completed | May 2, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:20 p.m.