Triple
T6611379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Penalty Kick |
E149244
|
entity |
| Predicate | feintingRule |
P72450
|
FINISHED |
| Object | feinting in the run-up is allowed |
—
|
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: feinting in the run-up is allowed | Statement: [The Penalty Kick, feintingRule, feinting in the run-up is allowed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feintingRule Context triple: [The Penalty Kick, feintingRule, feinting in the run-up is allowed]
-
A.
playedUnderRulesOf
Indicates that an activity or game was conducted in accordance with a specified set of rules or regulations.
-
B.
hasDesignatedPlayerRule
Indicates that a sports league or competition uses a designated player rule allowing certain players to be treated differently for roster or salary purposes.
-
C.
decidingPlayFumbleForcedBy
Indicates that a deciding play in a game is characterized by a fumble that was forced by a particular entity (e.g., player or team).
-
D.
emulates
Indicates that one entity imitates or reproduces the behavior, function, or characteristics of another.
-
E.
interceptionYardLine
Indicates the yard line on the field where an interception occurs during a play.
- F. None of above. chosen
Provenance (4 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_69c687ebc680819094caf71faba2efe2 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cf3796d08190a26e988386089447 |
completed | March 27, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69c6acfed25481909cac74c84a9fe088 |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6cf3683d08190b19e2aad30f2800f |
completed | March 27, 2026, 6:40 p.m. |
Created at: March 27, 2026, 1:57 p.m.