Triple
T34295810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nimrod R1 |
E880021
|
entity |
| Predicate | electronicSuite |
P88194
|
FINISHED |
| Object | specialised SIGINT equipment |
—
|
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: specialised SIGINT equipment | Statement: [Nimrod R1, electronicSuite, specialised SIGINT equipment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electronicSuite Context triple: [Nimrod R1, electronicSuite, specialised SIGINT equipment]
-
A.
isElectronicOnly
Indicates that the item or resource exists solely in digital form and is not available in any physical format.
-
B.
electronicState
Indicates the specific energy configuration or quantum state an entity occupies in an electronic or atomic system.
-
C.
electronicCompletion
Indicates that an action, process, or transaction has been fully completed through electronic or digital means rather than physically or manually.
-
D.
hasElectronicEffect
Indicates that one entity exerts or contributes an electronic influence or effect on another entity within a specified context.
-
E.
hasElectronicsFeature
chosen
Indicates that an entity possesses or is characterized by a specific electronic-related feature or capability.
- 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_69f349b79f6c81909cb468c92c39c74d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff17be6ad48190963206f2619b1b28 |
completed | May 9, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69ff1724ba24819092c928fcbcb286ec |
completed | May 9, 2026, 11:14 a.m. |
Created at: May 1, 2026, 1:57 a.m.