Triple
T29448126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSeries |
E746904
|
entity |
| Predicate | AirbusAcquisitionAnnouncement |
P15702
|
FINISHED |
| Object | 2017-10 |
—
|
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: 2017-10 | Statement: [CSeries, AirbusAcquisitionAnnouncement, 2017-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AirbusAcquisitionAnnouncement Context triple: [CSeries, AirbusAcquisitionAnnouncement, 2017-10]
-
A.
mergerAnnounced
Indicates that an official announcement has been made that two or more entities intend to merge into a single combined entity.
-
B.
acquisitionAnnouncedBy
chosen
Indicates that an acquisition event was publicly announced by the specified announcing entity (such as a company or organization).
-
C.
aircraftOrder
Indicates that one aircraft is positioned or sequenced before another in an ordered arrangement (such as a lineup, list, or schedule).
-
D.
aircraftManufacturerConsortium
Indicates a collaborative manufacturing relationship in which multiple organizations jointly produce or develop an aircraft.
-
E.
aircraftOnOrder
Indicates that an aircraft has been requested or purchased but has not yet been delivered or entered into service.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66b22beec8190978f4cf0f602fc20 |
completed | May 2, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:29 p.m.