Triple
T32703354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BAC 3-11 |
E836202
|
entity |
| Predicate | designOriginator |
P184
|
FINISHED |
| Object | British Aircraft Corporation |
—
|
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: British Aircraft Corporation | Statement: [BAC 3-11, designOriginator, British Aircraft Corporation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designOriginator Context triple: [BAC 3-11, designOriginator, British Aircraft Corporation]
-
A.
designedBy
chosen
Indicates that one entity is the creator, planner, or architect responsible for the form or structure of another entity.
-
B.
hasDesignOrigin
Indicates that one entity is the source, inspiration, or original model from which the design of another entity is derived.
-
C.
architectOrigin
Indicates that an architect originally comes from, or is associated with, a particular place or region.
-
D.
designLead
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
-
E.
designSucceededBy
Indicates that one design is followed or replaced by another design in a temporal or version sequence.
- 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_69f3493323288190a4e88251035fe96e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
Created at: May 1, 2026, 1:10 a.m.