Triple
T37396296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snoop Pearson |
E928861
|
entity |
| Predicate | hasCharacteristicWeapon |
P6014
|
FINISHED |
| Object | nail 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: nail gun | Statement: [Snoop Pearson, hasCharacteristicWeapon, nail gun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharacteristicWeapon Context triple: [Snoop Pearson, hasCharacteristicWeapon, nail gun]
-
A.
hasWeaponType
chosen
Indicates that an entity is associated with or equipped with a specific type or category of weapon.
-
B.
weaponryCarried
Indicates that one entity is carrying or equipped with a weapon or set of weapons in relation to another entity or context.
-
C.
hasWeaponOption
Indicates that an entity has a particular weapon available as a selectable or usable option.
-
D.
hasArmourCharacteristic
Indicates that an entity possesses a specific armour-related property or feature.
-
E.
hasWeaponForm
Indicates that one entity takes the form of, or is manifested as, a particular 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_69f76ebb10c481909b54b9dba263e29f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.