Triple
T13732902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crutches, Crosses, Caskets |
E329853
|
entity |
| Predicate | isHardHitting |
P16069
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Crutches, Crosses, Caskets, isHardHitting, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHardHitting Context triple: [Crutches, Crosses, Caskets, isHardHitting, true]
-
A.
isIntense
chosen
Indicates that something exhibits a high degree of strength, force, or concentration in its quality, effect, or activity.
-
B.
battingAggression
Indicates how aggressively a batter attempts to score runs, typically reflected in risk-taking and attacking shot selection.
-
C.
SilverSluggerOrEquivalent
Indicates that an entity has received a Silver Slugger award or an officially recognized equivalent offensive-performance award.
-
D.
usesStrikes
Indicates that one entity employs or relies on strikes as a method, tactic, or means to achieve a goal or exert influence over another entity or situation.
-
E.
typeOfStrike
Indicates the specific category or kind of strike involved in an event or action.
- 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de0201d3c48190aa306be231a28bc1 |
completed | April 14, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:55 p.m.