Triple
T19542780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Trophy Team Rifle Match |
E488948
|
entity |
| Predicate | typicalShootingPositions |
P17665
|
FINISHED |
| Object | standing |
—
|
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: standing | Statement: [National Trophy Team Rifle Match, typicalShootingPositions, standing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalShootingPositions Context triple: [National Trophy Team Rifle Match, typicalShootingPositions, standing]
-
A.
hasShootingPosition
Indicates that an entity has a designated location or spot from which shooting (e.g., firing a weapon or taking a shot) is performed.
-
B.
typicalShootingDistances
Indicates the usual or standard distances at which shooting (e.g., with a weapon or camera) typically occurs in a given context.
-
C.
shootingStyle
chosen
Indicates the characteristic manner or technique with which an entity performs a shooting action (e.g., in sports or photography).
-
D.
shootingRange
Indicates that one entity serves as a location or facility where another entity engages in shooting activities, typically for practice or training.
-
E.
hasShootingLocation
Indicates that an audiovisual work was filmed or recorded at a particular location.
- 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6387442588190a2cdae60a6a940d6 |
completed | April 20, 2026, 2:30 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.