Triple
T25460432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISSF World Championships |
E638030
|
entity |
| Predicate | includesDisciplineGroup |
P134380
|
FINISHED |
| Object | rifle |
—
|
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: rifle | Statement: [ISSF World Championships, includesDisciplineGroup, rifle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesDisciplineGroup Context triple: [ISSF World Championships, includesDisciplineGroup, rifle]
-
A.
includesDisciplineCategory
Indicates that one entity encompasses or contains a specific discipline category as part of its overall scope or classification.
-
B.
disciplineGroupOf
chosen
Indicates that one entity is a discipline group to which another entity (such as a person, course, or activity) belongs or is associated.
-
C.
hasDisciplineRole
Indicates that an entity holds a specific role or function within a particular discipline or field.
-
D.
hasDisciplineSections
Indicates that an entity is associated with one or more sections that belong to a particular discipline or field.
-
E.
supportsDiscipline
Indicates that one entity provides assistance, resources, or endorsement that helps sustain or advance a particular discipline.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 21, 2026, 2:11 p.m.