Triple
T35057402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayerische Motoren Werke AG |
E1011504
|
entity |
| Predicate | originallyProduced |
P182834
|
FINISHED |
| Object | aircraft engines |
—
|
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: aircraft engines | Statement: [Bayerische Motoren Werke AG, originallyProduced, aircraft engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyProduced Context triple: [Bayerische Motoren Werke AG, originallyProduced, aircraft engines]
-
A.
originallyProducedAs
Indicates that one entity was first created, released, or manufactured in the form of another specified entity or format.
-
B.
originallyProducedIn
Indicates that something was first created, manufactured, or brought into existence in a particular place or location.
-
C.
isProducedFrom
Indicates that something is created, generated, or derived from a specified source or input.
-
D.
originallyIn
Indicates that something first appeared, was created, or was initially located within a particular context, source, or place.
-
E.
hasOriginalProducer
chosen
Indicates that an entity was initially created, manufactured, or produced by a specific producer or organization.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.