Triple
T7991718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10th Mountain Division |
E186021
|
entity |
| Predicate | notableDeploymentType |
P20911
|
FINISHED |
| Object | rapid-response combat operations |
—
|
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-response combat operations | Statement: [10th Mountain Division, notableDeploymentType, rapid-response combat operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDeploymentType Context triple: [10th Mountain Division, notableDeploymentType, rapid-response combat operations]
-
A.
notableDeployment
Indicates that an entity has been deployed or launched in a way that is particularly significant, prominent, or widely recognized.
-
B.
deploymentType
Indicates the manner or configuration in which a system, application, or component is deployed or made operational.
-
C.
typeOfDeployment
Indicates the specific manner or configuration in which something (such as a system, application, or resource) is deployed or made operational.
-
D.
notableOperationType
chosen
Indicates that an entity is associated with a specific type or category of operation that is considered notable or significant.
-
E.
typicalDeployment
Indicates that one entity represents the standard or most commonly used deployment configuration or pattern for the other entity.
- 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_69ca829c6c308190ab05b43d234c52b2 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c712d0481908d163d2509d054fa |
completed | March 31, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69cb0483d3b48190b250c7603d747bca |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:16 p.m.