Triple
T37609647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackburn Botha |
E935751
|
entity |
| Predicate | designedForRequirement |
P86683
|
FINISHED |
| Object | Air Ministry Specification M.15/35 |
—
|
NE NERFINISHED |
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 Ministry Specification M.15/35 | Statement: [Blackburn Botha, designedForRequirement, Air Ministry Specification M.15/35]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForRequirement Context triple: [Blackburn Botha, designedForRequirement, Air Ministry Specification M.15/35]
-
A.
designedToMeetRequirement
chosen
Indicates that something has been intentionally created or configured in order to satisfy a specified requirement.
-
B.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
C.
basedOnRequirementOf
Indicates that something is established, created, or determined according to a specified requirement or set of requirements.
-
D.
developedFromRequirement
Indicates that something was created, designed, or derived based on a specific requirement.
-
E.
requiredDesignElement
Indicates that one entity must include, use, or incorporate another entity as a necessary design component or feature.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff891e4b9c8190aa86a339a8944496 |
completed | May 9, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69ff8801180c8190b23e20996ca68e0a |
completed | May 9, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:18 p.m.