Triple
T30979745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corporate Airlines |
E789330
|
entity |
| Predicate | operatedUnderBrandUntil |
P42229
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [Corporate Airlines, operatedUnderBrandUntil, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedUnderBrandUntil Context triple: [Corporate Airlines, operatedUnderBrandUntil, 2005]
-
A.
formerBrand
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
-
B.
operatedAsNameUntil
chosen
Indicates that an entity functioned or was known under a particular name up to a specified point in time.
-
C.
introducedUnderBrand
Indicates that one entity was launched, released, or brought to market using the branding or brand identity of another entity.
-
D.
formerlyMarketedBy
Indicates that an entity was previously marketed or promoted by another entity, but is no longer marketed by that same party.
-
E.
laterBrandOf
Indicates that one brand is a subsequent or successor brand to another, coming into use at a later time.
- 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff878f41888190bcb3bc41ad26081a |
completed | May 9, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69ff854082d88190aad3bfedf05e849f |
completed | May 9, 2026, 7:04 p.m. |
Created at: April 29, 2026, 8:55 p.m.