Triple
T467872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Marine Expeditionary Force |
E8488
|
entity |
| Predicate | militaryCapability |
P7256
|
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: [I Marine Expeditionary Force, militaryCapability, rapid deployment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryCapability Context triple: [I Marine Expeditionary Force, militaryCapability, rapid deployment]
-
A.
warfareCapability
Indicates the ability or capacity of an entity to engage in, conduct, or support acts of warfare.
-
B.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
-
C.
militaryCharacteristic
chosen
Indicates that one entity possesses a specific military-related attribute, quality, or feature in relation to another entity or context.
-
D.
militaryTechnology
Indicates that one entity is a type of military-related technology used for defense, combat, or warfare purposes.
-
E.
militaryFunction
Indicates a relationship where an entity serves a specific role, duty, or operational purpose within a military context.
- 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efd9bea081909ee782840f3da12b |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edebb3988190907992a584b4e260 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.