Triple
T19423640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Trophy Individual Rifle Match |
E485922
|
entity |
| Predicate | typicalFirearm |
P7745
|
FINISHED |
| Object | U.S. service rifle or equivalent |
—
|
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: U.S. service rifle or equivalent | Statement: [National Trophy Individual Rifle Match, typicalFirearm, U.S. service rifle or equivalent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFirearm Context triple: [National Trophy Individual Rifle Match, typicalFirearm, U.S. service rifle or equivalent]
-
A.
typicalWeapon
chosen
Indicates that the object is a weapon commonly or characteristically used by the subject.
-
B.
gunType
Indicates the specific category or kind of gun associated with an entity.
-
C.
gun
Indicates that one entity uses, carries, or is associated with a gun in relation to another entity or context.
-
D.
lightArmament
Indicates that an entity is equipped with or characterized by relatively minimal or lightweight weaponry compared to standard or heavy armament.
-
E.
ammunitionType
Indicates the specific kind or category of ammunition associated with or used by an 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e632169d9c81909a88704c6beb8fe0 |
completed | April 20, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.