Triple
T15377703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agent Whiskey |
E367711
|
entity |
| Predicate | weaponCharacteristic |
P76424
|
FINISHED |
| Object | electrified lasso |
—
|
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: electrified lasso | Statement: [Agent Whiskey, weaponCharacteristic, electrified lasso]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weaponCharacteristic Context triple: [Agent Whiskey, weaponCharacteristic, electrified lasso]
-
A.
weaponFeature
chosen
Indicates that one entity is a characteristic, attribute, or functional aspect of a weapon.
-
B.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
-
C.
militaryCharacteristic
Indicates that one entity possesses a specific military-related attribute, quality, or feature in relation to another entity or context.
-
D.
equipmentCharacteristic
Indicates that a specific characteristic, property, or attribute is associated with a piece of equipment.
-
E.
missionCharacteristic
Indicates that a mission possesses a specific attribute, feature, or quality that characterizes its nature or execution.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e5ece1081908d7c1289258b9c1f |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:18 a.m.