Triple
T29448135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSeries |
E746904
|
entity |
| Predicate | targetCompetition |
P191792
|
FINISHED |
| Object | Airbus A318 |
—
|
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 A318 | Statement: [CSeries, targetCompetition, Airbus A318]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetCompetition Context triple: [CSeries, targetCompetition, Airbus A318]
-
A.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
B.
competitionFrom
Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
-
C.
featuredCompetitionFor
Indicates that one entity is highlighted or promoted as a notable or primary competition associated with another entity.
-
D.
competitionDomain
Indicates that two or more entities are engaged in or associated with the same competitive context, field, or market.
-
E.
appliesToCompetition
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable specifically to a competition.
- 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_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
| PDg | Predicate description generation | batch_69fcec5e560481909cd710b88897e833 |
completed | May 7, 2026, 7:47 p.m. |
Created at: April 28, 2026, 3:29 p.m.