Triple
T32766386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SP5 (civilian variant) |
E837912
|
entity |
| Predicate | isNotCapableOf |
P52573
|
FINISHED |
| Object | select-fire operation |
—
|
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: select-fire operation | Statement: [SP5 (civilian variant), isNotCapableOf, select-fire operation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNotCapableOf Context triple: [SP5 (civilian variant), isNotCapableOf, select-fire operation]
-
A.
isCapableOf
Indicates that an entity has the ability or capacity to perform a particular action or function.
-
B.
notCompetentFor
chosen
Indicates that an entity lacks the necessary ability, qualification, or suitability to perform or handle another specified entity or task.
-
C.
consideredCapability
Indicates that something is regarded or evaluated as a potential capability of an entity.
-
D.
hasCap
Indicates that an entity possesses or is equipped with a cap or top covering.
-
E.
usedCapability
Indicates that an entity employed or exercised a particular capability, skill, or function in performing an action or achieving a result.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:13 a.m.