Triple
T22078518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skjold-class corvette |
E545583
|
entity |
| Predicate | electronicSystems |
P75566
|
FINISHED |
| Object | advanced combat management system |
—
|
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: advanced combat management system | Statement: [Skjold-class corvette, electronicSystems, advanced combat management system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electronicSystems Context triple: [Skjold-class corvette, electronicSystems, advanced combat management system]
-
A.
hasElectronicWarfareSystem
Indicates that an entity is equipped with or incorporates an electronic warfare system.
-
B.
avionics
Indicates that an entity is related to the electronic systems used to control, monitor, or assist the operation of aircraft or spacecraft.
-
C.
electricalSystem
Indicates that one entity functions as, is part of, or is directly related to the electrical system of another entity.
-
D.
hardwareComponent
chosen
Indicates that one entity is a physical hardware part or module that is contained in, attached to, or functionally part of another hardware system or device.
-
E.
avionicsSupplier
Indicates that one entity supplies avionics systems, components, or related services to another entity.
- 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_69e11e3523488190badd54b5d580c00d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128b43df0819090c248ded98fad12 |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:28 p.m.