Triple
T29454916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FuG 202 Lichtenstein B/C radar |
E747072
|
entity |
| Predicate | rangeAgainstBomber |
P83981
|
FINISHED |
| Object | about 4 km |
—
|
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: about 4 km | Statement: [FuG 202 Lichtenstein B/C radar, rangeAgainstBomber, about 4 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeAgainstBomber Context triple: [FuG 202 Lichtenstein B/C radar, rangeAgainstBomber, about 4 km]
-
A.
hasBomber
Indicates that an entity possesses, controls, or is associated with a bomber aircraft.
-
B.
typicalDetectionRangeAgainstBomber
chosen
Indicates the usual distance at which a system can detect a bomber target under standard conditions.
-
C.
isBomber
Indicates that an entity functions as or is classified as a bomber, typically designed or used to deliver explosive ordnance.
-
D.
mainBomberAircraft
Indicates that an entity serves as the primary bomber aircraft used by another entity (such as a military force, operation, or country).
-
E.
compatibleBomber
Indicates that one entity can function effectively as a bomber in conjunction with, or as a suitable counterpart to, another specified entity.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66b6c26a481908018e663aee7b269 |
completed | May 2, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:35 p.m.