Triple
T11501689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cossack sabers (shashka) |
E272677
|
entity |
| Predicate | alsoCapableOf |
P39122
|
FINISHED |
| Object | thrusting |
—
|
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: thrusting | Statement: [Cossack sabers (shashka), alsoCapableOf, thrusting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoCapableOf Context triple: [Cossack sabers (shashka), alsoCapableOf, thrusting]
-
A.
isCapableOf
chosen
Indicates that an entity has the ability or capacity to perform a particular action or function.
-
B.
isToolOf
Indicates that one entity functions as an instrument or means used by another entity to perform tasks or achieve goals.
-
C.
airCapability
Indicates that an entity possesses the ability or resources to operate or project power in the air (e.g., through aircraft, air defenses, or related systems).
-
D.
providesFunctionalityOf
Indicates that one entity supplies, implements, or makes available the capabilities or functions that are normally associated with another entity.
-
E.
landingCapability
Indicates the ability or suitability of an entity (e.g., a vehicle or system) to perform a landing under specified conditions.
- 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85de55cbc8190be71c2d03dc044f2 |
completed | April 10, 2026, 2:18 a.m. |
| PD | Predicate disambiguation | batch_69d808736c5c8190899b5b3b2e797f65 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.