Triple
T15756456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Düppel |
E381978
|
entity |
| Predicate | firstUsedAs |
P120211
|
FINISHED |
| Object | airborne radar countermeasure |
—
|
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: airborne radar countermeasure | Statement: [Düppel, firstUsedAs, airborne radar countermeasure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUsedAs Context triple: [Düppel, firstUsedAs, airborne radar countermeasure]
-
A.
firstUsedFor
Indicates that one entity was the earliest or original thing for which another entity was used or applied.
-
B.
firstUsedAt
Indicates the time or place at which something was initially used or put into operation.
-
C.
firstUsedBy
Indicates that something was initially utilized, applied, or employed by a particular entity before any others.
-
D.
firstUsedOn
Indicates the date, time, or context in which something was initially applied, activated, or put into use on a particular object or entity.
-
E.
firstUsedInEvent
Indicates that something (such as an object, method, or concept) was used for the first time during a specified event.
- F. None of above. chosen
Provenance (4 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e050b1ff4881909d5240d1d30f5c8b |
completed | April 16, 2026, 3 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e03cc871d0819085c0fc54de7984ff |
completed | April 16, 2026, 1:35 a.m. |
Created at: April 10, 2026, 4:47 a.m.