Triple
T11087684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Glasgow (D88) |
E262163
|
entity |
| Predicate | electronics |
P75566
|
FINISHED |
| Object | radar and fire-control systems for Sea Dart |
—
|
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: radar and fire-control systems for Sea Dart | Statement: [HMS Glasgow (D88), electronics, radar and fire-control systems for Sea Dart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electronics Context triple: [HMS Glasgow (D88), electronics, radar and fire-control systems for Sea Dart]
-
A.
circuit
Indicates that one entity forms or participates in an electrical or logical pathway that allows current or signals to flow through a connected system involving another entity.
-
B.
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.
-
C.
hardwareCategory
Indicates that an item belongs to or is classified under a specific hardware category or type.
-
D.
circuitDesigner
Indicates that an entity is responsible for designing or creating electronic circuits for another entity or system.
-
E.
hardwareDesign
Indicates a relationship where one entity is responsible for creating, specifying, or engineering the physical components and architecture of another entity’s hardware system.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799c5008081908f59612243fa4f7a |
completed | April 9, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.