Triple
T18334010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Matrix |
E439219
|
entity |
| Predicate | weaponProficiency |
P131403
|
FINISHED |
| Object | firearms |
—
|
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: firearms | Statement: [John Matrix, weaponProficiency, firearms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weaponProficiency Context triple: [John Matrix, weaponProficiency, firearms]
-
A.
weaponDiscipline
Indicates that an entity practices, adheres to, or is governed by a particular system, style, or code of weapon use or combat training.
-
B.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
-
C.
weaponForgedFor
Indicates that a weapon was specifically created or crafted for a particular entity, purpose, or context.
-
D.
weaponFeature
Indicates that one entity is a characteristic, attribute, or functional aspect of a weapon.
-
E.
weaponForged
Indicates that one entity has been created or shaped as a weapon by another entity through a forging process.
- 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50ecbc76c8190a80c0c8c8bce1cbd |
completed | April 19, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e4561d665081908ec555344e76d82b |
completed | April 19, 2026, 4:12 a.m. |
Created at: April 10, 2026, 10:36 a.m.