Triple
T19114513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Service Pistol Championships |
E467872
|
entity |
| Predicate | primarySkillTested |
P134480
|
FINISHED |
| Object | accuracy |
—
|
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: accuracy | Statement: [Service Pistol Championships, primarySkillTested, accuracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySkillTested Context triple: [Service Pistol Championships, primarySkillTested, accuracy]
-
A.
skillAssessed
Indicates that an entity’s skill or competency has been evaluated or measured, typically by another agent or process.
-
B.
indicatesSkill
Indicates a relationship where one entity possesses, demonstrates, or is associated with a particular skill represented by another entity.
-
C.
skillType
Indicates the specific category or kind of skill that characterizes or classifies an associated skill-related entity or action.
-
D.
primaryCapability
Indicates that one entity serves as the main or most important functional ability, role, or competence of another entity.
-
E.
skilledIn
Indicates that an entity possesses ability, expertise, or proficiency in performing or using another entity (such as a task, tool, 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.