Triple
T8382428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hardest Shot |
E197724
|
entity |
| Predicate | goalPresence |
P75913
|
FINISHED |
| Object | shot is typically taken toward an empty net |
—
|
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: shot is typically taken toward an empty net | Statement: [Hardest Shot, goalPresence, shot is typically taken toward an empty net]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalPresence Context triple: [Hardest Shot, goalPresence, shot is typically taken toward an empty net]
-
A.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
B.
goalStatementIncludes
chosen
Indicates that a goal statement contains or explicitly mentions a particular element, concept, or condition.
-
C.
hasPlanningGoal
Indicates that an entity is associated with, or directed toward achieving, a specific planning objective or target state.
-
D.
goalStage
Indicates the specific phase or step a goal is currently in within its overall progression or lifecycle.
-
E.
hasHumanPresence
Indicates that humans are physically present in or occupying a given location, object, or context.
- 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_69ca82f64c188190af4e1608036b865d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80ddc0f08190a90d4d9070bf713b |
completed | March 31, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69cb70cfe82881909fe374ba52649e84 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:02 p.m.