Triple
T26190808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blohm & Voss BV 155 |
E654955
|
entity |
| Predicate | airIntakeFeature |
P89402
|
FINISHED |
| Object | chin radiator installation |
—
|
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: chin radiator installation | Statement: [Blohm & Voss BV 155, airIntakeFeature, chin radiator installation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airIntakeFeature Context triple: [Blohm & Voss BV 155, airIntakeFeature, chin radiator installation]
-
A.
airIntakeType
Indicates the type or configuration of the system or mechanism used to draw air into an engine or device.
-
B.
airIntakeLocation
Indicates the physical position or area where air is drawn into a system, device, or structure.
-
C.
airIntakeIntegration
chosen
Indicates how an air intake component is incorporated or connected into a larger system or assembly.
-
D.
ventilationFeature
Indicates that one entity has a structural or functional role related to providing, enabling, or affecting ventilation for another entity.
-
E.
intake
Indicates the act of taking something in or consuming it, such as food, drink, or other substances, into a system or organism.
- 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60ca25acc81908bfe2d4ba1107748 |
completed | May 2, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:44 p.m.