Triple
T6648886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goal kick |
E150768
|
entity |
| Predicate | relatedRestart |
P72048
|
FINISHED |
| Object | Corner kick |
—
|
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: Corner kick | Statement: [Goal kick, relatedRestart, Corner kick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedRestart Context triple: [Goal kick, relatedRestart, Corner kick]
-
A.
relaunch
Indicates restarting or bringing back into operation something that was previously launched, often with changes or improvements.
-
B.
reignRestart
Indicates that a ruler’s period of governance has begun again after an interruption or previous end.
-
C.
rebootOf
Indicates that one work is a new version that restarts or reimagines the story, continuity, or franchise of another earlier work.
-
D.
renews
Indicates that one entity extends, refreshes, or restores the validity, duration, or effectiveness of another entity, often continuing a prior agreement, state, or condition.
-
E.
re-establishedAfter
Indicates that a relationship or state was previously ended or inactive and then brought back into effect following a specified event or time.
- 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_69c687f1a3048190828b7342f7125d5c |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad04d66c8190926ffcbff372643b |
completed | March 27, 2026, 4:15 p.m. |
| PDg | Predicate description generation | batch_69c6cc988c0081909d22b86ca299331c |
completed | March 27, 2026, 6:29 p.m. |
Created at: March 27, 2026, 2:01 p.m.