Triple
T6685425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corner kick |
E152088
|
entity |
| Predicate | restartLocation |
P389
|
FINISHED |
| Object | Corner arc |
—
|
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 arc | Statement: [Corner kick, restartLocation, Corner arc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restartLocation Context triple: [Corner kick, restartLocation, Corner arc]
-
A.
reentryLocation
Indicates the place or area where an entity returns or re-enters after having left or exited a previous location or state.
-
B.
seasonResumptionLocation
Indicates the location where a season (such as a sports league or series) is resumed after a break or interruption.
-
C.
repeatLocation
Indicates that an entity occurs or appears multiple times at the same location or position.
-
D.
startPoint
chosen
Indicates the initial location or position from which an object, path, or action begins.
-
E.
launchLocation
Indicates the place or site from which something is launched or set into motion.
- 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_69c687f9977c819097e7f5ada4fe522e |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cd0fa5188190a23281cb09d98139 |
completed | March 27, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69c6ad0d3c1081908dadff7a6a054123 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:04 p.m.