Triple
T38273153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mordecai "Three Finger" Brown |
E1021270
|
entity |
| Predicate | effectOfInjury |
P175672
|
FINISHED |
| Object | enhanced grip on the baseball |
—
|
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: enhanced grip on the baseball | Statement: [Mordecai "Three Finger" Brown, effectOfInjury, enhanced grip on the baseball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOfInjury Context triple: [Mordecai "Three Finger" Brown, effectOfInjury, enhanced grip on the baseball]
-
A.
consequenceOfInjury
chosen
Indicates that one event, condition, or outcome occurs as a direct result of a specified injury.
-
B.
causeOfInjury
Indicates that one entity is the source or reason that another entity sustained an injury.
-
C.
injuryType
Indicates the specific kind or category of injury associated with an entity or event.
-
D.
injuryPlotPoint
Indicates that an event in the narrative involves a character being injured, serving as a significant plot development or turning point.
-
E.
hasPlaceOfInjury
Indicates that an injury occurred at a specific place or location.
- 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_69f76dee198c8190bf5109421e47a658 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
Created at: May 3, 2026, 4:30 p.m.