Triple
T31575623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GLEX |
E805689
|
entity |
| Predicate | relatedToManufacturer |
P207461
|
FINISHED |
| Object | Bombardier Aerospace |
E1590839
|
NE 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: Bombardier Aerospace | Statement: [GLEX, relatedToManufacturer, Bombardier Aerospace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToManufacturer Context triple: [GLEX, relatedToManufacturer, Bombardier Aerospace]
-
A.
relatedToProduct
Indicates a general association or connection between an entity and a specific product, without specifying the exact nature of that relationship.
-
B.
relatedToSpecification
Indicates that something has a connection or relevance to a particular specification, standard, or set of defined requirements.
-
C.
relatedToPart
Indicates that one entity has a connection or association with a specific part or component of another entity.
-
D.
alsoManufacturedBy
Indicates that an item or product is produced by an additional manufacturer beyond the primary or previously mentioned one.
-
E.
usedManufacturer
Indicates that an entity has employed or sourced products, components, or services from a particular manufacturer.
- F. None of above. chosen
Provenance (5 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b5648a71c8190a7741768ed3c80f4 |
completed | June 12, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 30, 2026, 10:21 p.m.