Triple
T29448125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSeries |
E746904
|
entity |
| Predicate | programAcquiredBy |
P173261
|
FINISHED |
| Object | Airbus |
—
|
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: Airbus | Statement: [CSeries, programAcquiredBy, Airbus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programAcquiredBy Context triple: [CSeries, programAcquiredBy, Airbus]
-
A.
announcedProgram
Indicates that an entity has publicly communicated or declared the existence or details of a particular program.
-
B.
offersSyndicatedProgramming
Indicates that one entity provides syndicated programming content for distribution or broadcast by another entity.
-
C.
stationProgram
Indicates a relationship where a specific program is associated with, broadcast by, or scheduled on a particular station.
-
D.
televisionPlatform
Indicates that one entity serves as the television platform (e.g., service, system, or distribution channel) through which the other entity’s TV content is delivered or accessed.
-
E.
servedByTelevisionStation
Indicates that a particular area, audience, or service region is provided television broadcasting or coverage by a specific television station.
- F. None of above. chosen
Provenance (4 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_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 28, 2026, 3:29 p.m.