Triple
T4319378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st (United Kingdom) Division |
E96473
|
entity |
| Predicate | associatedCapability |
P56209
|
FINISHED |
| Object | rapid deployment |
—
|
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: rapid deployment | Statement: [1st (United Kingdom) Division, associatedCapability, rapid deployment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCapability Context triple: [1st (United Kingdom) Division, associatedCapability, rapid deployment]
-
A.
consideredCapability
Indicates that something is regarded or evaluated as a potential capability of an entity.
-
B.
usedCapability
Indicates that an entity employed or exercised a particular capability, skill, or function in performing an action or achieving a result.
-
C.
plannedCapability
Indicates that an entity is intended or scheduled to possess or provide a particular capability in the future.
-
D.
couplingCapability
Indicates the ability or suitability of one entity to connect, link, or interface with another in a functional or compatible manner.
-
E.
providesCapabilityTo
Indicates that one entity enables or equips another entity with a specific capability or functionality.
- 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_69b345422aac81909ddbadae437d122e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35112ec008190958487f501481887 |
completed | March 12, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69b34f4bec888190987fc2631498b637 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3501834448190bedf775a80da4778 |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:12 p.m.