Triple
T29559862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hirschgeweih |
E750008
|
entity |
| Predicate | hasDetectionRole |
P193717
|
FINISHED |
| Object | air-to-air target acquisition |
—
|
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: air-to-air target acquisition | Statement: [Hirschgeweih, hasDetectionRole, air-to-air target acquisition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDetectionRole Context triple: [Hirschgeweih, hasDetectionRole, air-to-air target acquisition]
-
A.
hasModeOfDetection
Indicates that one entity is identified, measured, or observed using a specified method or technique of detection.
-
B.
requiresDetectionOf
Indicates that one entity can only occur, be valid, or proceed if another entity has first been detected or identified.
-
C.
isDetector
Indicates that one entity functions as a detector for, or is responsible for detecting, another entity or phenomenon.
-
D.
mainDetector
Indicates that an entity serves as the primary or principal detector in relation to another entity or system.
-
E.
detected
Indicates that an entity has observed, identified, or discovered the presence or occurrence of another entity or 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
| PDg | Predicate description generation | batch_69fd509cdc5c8190a5f2c451bc0d0b25 |
completed | May 8, 2026, 2:55 a.m. |
Created at: April 28, 2026, 5:18 p.m.