Triple
T24825910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luftwaffe (planned) |
E621188
|
entity |
| Predicate | intendedEquipmentType |
P157750
|
FINISHED |
| Object | rocket interceptors |
—
|
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: rocket interceptors | Statement: [Luftwaffe (planned), intendedEquipmentType, rocket interceptors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedEquipmentType Context triple: [Luftwaffe (planned), intendedEquipmentType, rocket interceptors]
-
A.
intendedEquipmentType
chosen
Indicates that a particular piece of equipment is the planned or designated type to be used in a given context or activity.
-
B.
typeOfEquipmentUsed
Indicates that a particular piece or category of equipment is utilized in performing a specific action, process, or activity.
-
C.
testedDeviceType
Indicates that one entity is the type or category of device on which another entity has been tested.
-
D.
intendedEngineType
Indicates that an entity is designed or specified to use a particular type of engine.
-
E.
targetedDevice
Indicates that one entity is the specific device toward which another entity’s action, effect, or configuration is directed.
- 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_69e2fac0c3b881909110e5a56c6fa46f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 5:05 a.m.