Triple
T25500633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blohm & Voss BV 141 |
E639099
|
entity |
| Predicate | reasonForLimitedProduction |
P87364
|
FINISHED |
| Object | competition from Focke-Wulf Fw 189 |
—
|
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: competition from Focke-Wulf Fw 189 | Statement: [Blohm & Voss BV 141, reasonForLimitedProduction, competition from Focke-Wulf Fw 189]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForLimitedProduction Context triple: [Blohm & Voss BV 141, reasonForLimitedProduction, competition from Focke-Wulf Fw 189]
-
A.
reasonForNoProduction
Indicates the specific cause or explanation for why production did not occur.
-
B.
reasonForPerformanceLimitation
Indicates that one factor serves as the cause or explanation for why a performance limitation occurs.
-
C.
productionRestrictedTo
Indicates that the production or manufacture of something is limited or confined to a specified location, entity, or set of conditions.
-
D.
productionConstraint
chosen
Indicates a limiting condition or rule that restricts how, when, or how much something can be produced.
-
E.
limitedIssueOf
Indicates that one entity is issued or made available in a restricted or finite quantity by another 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 21, 2026, 2:42 p.m.