Triple
T11833209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German Navy destroyer Lütjens (D185) |
E281444
|
entity |
| Predicate | hasElectronicSystems |
P88194
|
FINISHED |
| Object | radar |
—
|
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 | Statement: [German Navy destroyer Lütjens (D185), hasElectronicSystems, radar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectronicSystems Context triple: [German Navy destroyer Lütjens (D185), hasElectronicSystems, radar]
-
A.
hasDigitalSystem
Indicates that an entity possesses, uses, or is equipped with a digital system (such as software, hardware, or an integrated digital platform).
-
B.
hasElectronicsFeature
chosen
Indicates that an entity possesses or is characterized by a specific electronic-related feature or capability.
-
C.
hasElectronicWarfareSystem
Indicates that an entity is equipped with or incorporates an electronic warfare system.
-
D.
hasCommunicationSystems
Indicates that one entity is equipped with or possesses communication systems used for transmitting or receiving information.
-
E.
isMechanicalOrElectronic
Indicates that something operates using mechanical components, electronic components, or a combination of both.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a62e7e408190998bebe346c82e89 |
completed | April 10, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.