Triple
T17130515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papasha |
E415709
|
entity |
| Predicate | associatedWeaponType |
P67648
|
FINISHED |
| Object | submachine gun |
—
|
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: submachine gun | Statement: [Papasha, associatedWeaponType, submachine gun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWeaponType Context triple: [Papasha, associatedWeaponType, submachine gun]
-
A.
associatedWithWeapon
Indicates that an entity has a connection or involvement with a weapon, such as ownership, use, presence, or relevance in a given context.
-
B.
relatedToWeaponType
chosen
Indicates that an entity has an association or connection with a specific type or category of weapon.
-
C.
typicalWeapon
Indicates that the object is a weapon commonly or characteristically used by the subject.
-
D.
hasWeaponType
Indicates that an entity is associated with or equipped with a specific type or category of weapon.
-
E.
involvesWeaponType
Indicates that the relationship or action includes the use, presence, or association of a specific type or category of weapon.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f029d1a48190a9d4094827d11d23 |
completed | April 18, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.