Triple
T4529056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flybe |
E106248
|
entity |
| Predicate | stockExchangeDelistingYear |
P51857
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Flybe, stockExchangeDelistingYear, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stockExchangeDelistingYear Context triple: [Flybe, stockExchangeDelistingYear, 2019]
-
A.
relistedOnExchangeYear
Indicates the year in which an entity was relisted on a stock exchange after having been previously delisted or removed.
-
B.
delisted
chosen
Indicates that an entity has been removed from an official list, registry, or exchange where it was previously included.
-
C.
USMarketWithdrawalYear
Indicates the year in which a product, service, or entity was withdrawn from the United States market.
-
D.
wasDissolvedAfter
Indicates that one entity ceased to exist or operate at a later point in time than another entity’s dissolution.
-
E.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
- 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_69bd43f3d6e08190a91824f833d51bbe |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd5779593081908593537b9239e01b |
completed | March 20, 2026, 2:19 p.m. |
| PD | Predicate disambiguation | batch_69bd521cf77c819083852de3094d1377 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:03 p.m.