Triple
T28897998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Morris |
E732879
|
entity |
| Predicate | usesSubWeapons |
P706
|
FINISHED |
| Object | throwing axe |
—
|
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: throwing axe | Statement: [John Morris, usesSubWeapons, throwing axe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSubWeapons Context triple: [John Morris, usesSubWeapons, throwing axe]
-
A.
secondaryArmament
Indicates that one entity serves as a secondary or auxiliary weapon system associated with another primary platform or armament.
-
B.
supportsWeapon
Indicates that one entity is capable of accommodating, using, or being compatible with a specified weapon.
-
C.
usedWeapon
chosen
Indicates that an entity employed a specific weapon as the means or tool to carry out an action or event.
-
D.
specialWeapon
Indicates that an entity is a weapon with unique, enhanced, or otherwise exceptional properties compared to standard weapons.
-
E.
secondaryWeaponTechnology
Indicates that one entity serves as a secondary or backup weapon system or technology associated with 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 28, 2026, 8 a.m.