Triple
T37140273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destroyer Squadron 15 |
E920085
|
entity |
| Predicate | forwardDeployed |
P12777
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Destroyer Squadron 15, forwardDeployed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forwardDeployed Context triple: [Destroyer Squadron 15, forwardDeployed, true]
-
A.
deploys
Indicates the action of strategically placing or releasing something into operation or use, often in a specific context or location.
-
B.
foreignDeployment
chosen
Indicates that an entity is deployed or stationed outside its own country or usual national territory.
-
C.
deployedFor
Indicates that one entity is deployed or put into operational use to serve, support, or act on behalf of another entity.
-
D.
primaryDeployment
Indicates that one deployment is designated as the main or most important deployment among multiple possible deployments for an entity.
-
E.
frontsDeployed
Indicates that a military or operational force has been positioned and activated across one or more fronts or areas of engagement.
- 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_69f76e9e9d008190a250b0387c992c74 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.