Triple
T6611367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Penalty Kick |
E149244
|
entity |
| Predicate | restartType |
P11249
|
FINISHED |
| Object | restart of play after a stoppage |
—
|
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: restart of play after a stoppage | Statement: [The Penalty Kick, restartType, restart of play after a stoppage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restartType Context triple: [The Penalty Kick, restartType, restart of play after a stoppage]
-
A.
starterType
Indicates the classification or category of a starter (e.g., initial component, opening item, or first phase) associated with an entity or process.
-
B.
restartCapability
Indicates the ability or permission for an entity to be restarted, typically after a stop, failure, or configuration change.
-
C.
resetType
chosen
Indicates the specific kind or method of reset applied to an entity, process, or system state.
-
D.
startFinishType
Indicates the specific way in which an activity, event, or process begins and/or ends (e.g., its initiation and completion characteristics).
-
E.
reignRestart
Indicates that a ruler’s period of governance has begun again after an interruption or previous end.
- 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_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. |
Created at: March 27, 2026, 1:57 p.m.