Triple
T18676896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tackle |
E456622
|
entity |
| Predicate | isGoalLineStand |
P132262
|
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: [The Tackle, isGoalLineStand, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGoalLineStand Context triple: [The Tackle, isGoalLineStand, true]
-
A.
ownGoalDirectlyAllowed
Indicates that an own goal is permitted to be scored directly, without requiring any intervening touch or event.
-
B.
infringementByGoalkeeperOutcome
Indicates that a rules infringement committed by the goalkeeper has led to a specific recorded outcome or result in the context of play.
-
C.
goldenGoalRuleUsed
Indicates that the outcome of a match or competition was determined using the golden goal rule, where the first score in extra time immediately ends the game.
-
D.
refereeSignal
Indicates that a referee communicates a decision or instruction through an official signal (e.g., whistle, gesture, or flag) regarding an event in the game.
-
E.
goalkeeperAction
Indicates actions performed by a goalkeeper in the context of defending the goal, such as saving, catching, blocking, or distributing the ball.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e556b66680819082a268f1bf857db5 |
completed | April 19, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:48 a.m.