Triple
T29146190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Accuracy Shooting |
E738780
|
entity |
| Predicate | targetsLocation |
P43296
|
FINISHED |
| Object | corners of the goal |
—
|
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: corners of the goal | Statement: [Accuracy Shooting, targetsLocation, corners of the goal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsLocation Context triple: [Accuracy Shooting, targetsLocation, corners of the goal]
-
A.
targetLocation
chosen
Indicates the specific place or destination toward which an action, movement, or effect is directed.
-
B.
locates
Indicates that one entity determines, specifies, or identifies the position or place of another entity in space or within a given context.
-
C.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified by another entity.
-
D.
coreLocation
Indicates that one entity serves as the central or primary location associated with another entity.
-
E.
targetsSource
Indicates that something is directed at, aimed toward, or focused on a specified source as its primary origin or object.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 28, 2026, 11:39 a.m.