Triple
T26387390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Run and shoot offense |
E663317
|
entity |
| Predicate | commonCriticism |
P62059
|
FINISHED |
| Object | can expose quarterback to hits |
—
|
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: can expose quarterback to hits | Statement: [Run and shoot offense, commonCriticism, can expose quarterback to hits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonCriticism Context triple: [Run and shoot offense, commonCriticism, can expose quarterback to hits]
-
A.
typeOfCriticism
Indicates that one entity is a specific kind or category of criticism directed at another entity or subject.
-
B.
criticismReason
chosen
Indicates that one entity criticizes another entity specifically because of the stated reason.
-
C.
hasCriticism
Indicates that one entity expresses disapproval, objection, or negative evaluation directed toward another entity.
-
D.
criticizedFor
Indicates that one entity expresses disapproval or negative judgment of another entity specifically because of a particular action, quality, or outcome.
-
E.
criticizedConstruct
Indicates that one entity expressed disapproval or negative judgment about another entity’s constructed work, idea, or creation.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 26, 2026, 11:23 p.m.