Triple
T32970356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avro Vulcan (early design work) |
E843496
|
entity |
| Predicate | aimedToMeet |
P107402
|
FINISHED |
| Object | British Air Ministry bomber requirements |
—
|
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: British Air Ministry bomber requirements | Statement: [Avro Vulcan (early design work), aimedToMeet, British Air Ministry bomber requirements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimedToMeet Context triple: [Avro Vulcan (early design work), aimedToMeet, British Air Ministry bomber requirements]
-
A.
hadGoal
chosen
Indicates that an entity previously possessed or pursued a particular goal or objective.
-
B.
aimedToConnect
Indicates an intention or effort by one entity to establish a link, relationship, or communication channel with another entity.
-
C.
aimedToLimit
Indicates an action or policy that was intentionally directed toward restricting, reducing, or constraining something.
-
D.
aimedToGrant
Indicates an intention or effort to provide or confer something (such as a right, benefit, or permission) to a recipient.
-
E.
meets
Indicates that two or more entities come together at the same place and time, typically for interaction or a shared purpose.
- 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_69f3494b9fc48190bb61c955ba471275 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d1aa6c6481909e8e2968d4f3029d |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:21 a.m.