Triple
T29559834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hirschgeweih |
E750008
|
entity |
| Predicate | appliedToDevice |
P86660
|
FINISHED |
| Object | FuG 220 Lichtenstein SN-2 radar |
—
|
NE NERFINISHED |
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: FuG 220 Lichtenstein SN-2 radar | Statement: [Hirschgeweih, appliedToDevice, FuG 220 Lichtenstein SN-2 radar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToDevice Context triple: [Hirschgeweih, appliedToDevice, FuG 220 Lichtenstein SN-2 radar]
-
A.
announcedWithDevice
Indicates that an announcement or communication was made using a specific device as the medium or tool.
-
B.
testedDevice
Indicates that one entity has performed a test on, or experimentally evaluated, another entity as a device.
-
C.
targetedDevice
chosen
Indicates that one entity is the specific device toward which another entity’s action, effect, or configuration is directed.
-
D.
usesDevice
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
E.
occursInDevice
Indicates that an event, process, or phenomenon takes place within or inside a specified device.
- 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: April 28, 2026, 5:18 p.m.