Triple
T19114490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smallbore Rifle Championships |
E467871
|
entity |
| Predicate | rangeEnvironment |
P134479
|
FINISHED |
| Object | outdoor range |
—
|
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: outdoor range | Statement: [Smallbore Rifle Championships, rangeEnvironment, outdoor range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeEnvironment Context triple: [Smallbore Rifle Championships, rangeEnvironment, outdoor range]
-
A.
rangeRegion
Indicates that one entity defines or corresponds to the spatial or conceptual region over which another entity extends or is applicable.
-
B.
rangeRole
Indicates that the specified role is associated with, or applies to, the range (target) of a property or relationship.
-
C.
rangeEPA
Indicates the EPA-rated driving range that a vehicle can travel on a single charge or tank under standardized test conditions.
-
D.
range
Indicates that a value, property, or effect extends between specified limits or over a specified interval or scope.
-
E.
realmWithin
Indicates that one realm or domain is contained inside, or exists as a subset of, another realm or domain.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e39617408190b5134918f54f9c52 |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:05 p.m.