Triple
T17174626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | women's sabre |
E416826
|
entity |
| Predicate | attackTypesAllowed |
P126609
|
FINISHED |
| Object | cutting |
—
|
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: cutting | Statement: [women's sabre, attackTypesAllowed, cutting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackTypesAllowed Context triple: [women's sabre, attackTypesAllowed, cutting]
-
A.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
B.
attackFeasibility
Indicates the extent to which carrying out an attack is practically possible given current conditions, capabilities, and constraints.
-
C.
attacksIf
Indicates that one entity initiates or carries out an attack on another entity when certain conditions are met.
-
D.
attacks
Indicates that one entity initiates an aggressive or harmful action directed toward another entity.
-
E.
securityTypePermitted
Indicates that a particular type or category of security is allowed or authorized within a given context or system.
- F. None of above. chosen
Provenance (4 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc0c329081909f118bd4b7be8653 |
completed | April 18, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e39c2fedb881908bfed2c3e5f2616a |
completed | April 18, 2026, 2:58 p.m. |
Created at: April 10, 2026, 5:37 a.m.