Triple
T21718572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gearing-class destroyer |
E536093
|
entity |
| Predicate | FRAMUpgradesIncluded |
P5357
|
FINISHED |
| Object | enhanced anti-submarine sensors |
—
|
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: enhanced anti-submarine sensors | Statement: [Gearing-class destroyer, FRAMUpgradesIncluded, enhanced anti-submarine sensors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FRAMUpgradesIncluded Context triple: [Gearing-class destroyer, FRAMUpgradesIncluded, enhanced anti-submarine sensors]
-
A.
wasUpgradedFor
Indicates that one entity was improved, enhanced, or updated specifically to serve, benefit, or be compatible with another entity.
-
B.
firmwareUpgradable
Indicates that a device’s firmware can be updated or replaced after deployment, typically through software-based upgrade mechanisms.
-
C.
hasUpgradeSystem
Indicates that an entity includes or is equipped with a system for performing upgrades or enhancements.
-
D.
hasUpgrade
chosen
Indicates that one entity possesses, includes, or is associated with an improved or enhanced version of another entity.
-
E.
partOfUpgrade
Indicates that one entity is included as a component or step within a larger upgrade process or package.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd96cc58081908dda09819041b888 |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:47 p.m.