Triple
T14485798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCALP Naval |
E359225
|
entity |
| Predicate | designedForTargetType |
P9903
|
FINISHED |
| Object | high-value land targets |
—
|
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: high-value land targets | Statement: [SCALP Naval, designedForTargetType, high-value land targets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForTargetType Context triple: [SCALP Naval, designedForTargetType, high-value land targets]
-
A.
supportsTargetType
Indicates that one entity is capable of operating with, handling, or being compatible with a specified target type.
-
B.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
C.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
-
D.
usesTarget
Indicates that one entity employs, applies, or operates on another entity as its target or object of action.
-
E.
primaryTargetType
chosen
Indicates the main category or type of entity that is the principal focus or intended recipient of an action, effect, or operation.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924ee0f08190baf68318b41fa64d |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.