Triple
T38593186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heavy Pulse Rifle |
E932499
|
entity |
| Predicate | aimType |
P81650
|
FINISHED |
| Object | player-aimed weapon |
—
|
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: player-aimed weapon | Statement: [Heavy Pulse Rifle, aimType, player-aimed weapon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimType Context triple: [Heavy Pulse Rifle, aimType, player-aimed weapon]
-
A.
aimingMethod
chosen
Indicates the technique or approach used to direct or aim an action, object, or effect toward a target.
-
B.
aimsToCapture
Indicates an intention or effort by one entity to take control of, seize, or gain possession of another entity.
-
C.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
D.
attackTargetType
Indicates the type or category of target that an attack is directed against.
-
E.
aimsToDetect
Indicates an intention or designed purpose to discover, identify, or recognize the presence or characteristics of something.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.