Triple
T19114518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Service Pistol Championships |
E467872
|
entity |
| Predicate | ruleEmphasis |
P17414
|
FINISHED |
| Object | use of standard-issue style equipment |
—
|
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: use of standard-issue style equipment | Statement: [Service Pistol Championships, ruleEmphasis, use of standard-issue style equipment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruleEmphasis Context triple: [Service Pistol Championships, ruleEmphasis, use of standard-issue style equipment]
-
A.
hasEmphasis
chosen
Indicates that one element is given special stress, importance, or prominence relative to others.
-
B.
normativelyEmphasizes
Indicates that one entity highlights, prioritizes, or stresses another entity as a standard, value, or principle that ought to be followed or given special importance.
-
C.
strategyEmphasis
Indicates an entity’s primary focus or priority within a broader strategy or plan.
-
D.
strictRule
Indicates that a rule is enforced rigidly, allowing no exceptions, flexibility, or deviation in its application.
-
E.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
- 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_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. |
Created at: April 10, 2026, 12:05 p.m.