Triple
T4910724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Forces Component Command |
E110223
|
entity |
| Predicate | canDeployTo |
P27682
|
FINISHED |
| Object | foreign 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: foreign operations | Statement: [Special Forces Component Command, canDeployTo, foreign operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canDeployTo Context triple: [Special Forces Component Command, canDeployTo, foreign operations]
-
A.
canBeDeployedUnder
chosen
Indicates that one entity is permitted or suitable to be deployed or operated under the conditions, context, or authority defined by another entity.
-
B.
hasDeployment
Indicates that an entity is associated with or utilizes a specific deployment instance (e.g., of software, a model, or a system) in an operational context.
-
C.
deployedTo
Indicates that something (such as a resource, application, or unit) has been placed, installed, or made operational in a specific target environment or location.
-
D.
deploymentCapability
Indicates the ability or capacity of an entity to deploy, release, or roll out another entity (such as a system, service, or resource) into an operational environment.
-
E.
isDeployedFrom
Indicates that one entity originates, is launched, or put into operation from another specified source or location.
- 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_69bd44132b94819088522d92beaadc78 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e9acc0c819080b07e2e7924d163 |
completed | March 20, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69bd6c325e188190823836d79934e9bc |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.