Triple
T4529052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flybe |
E106248
|
entity |
| Predicate | acquisitionOfBAConnectCompleted |
P23562
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Flybe, acquisitionOfBAConnectCompleted, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquisitionOfBAConnectCompleted Context triple: [Flybe, acquisitionOfBAConnectCompleted, 2007]
-
A.
acquisitionResultedIn
Indicates that an acquisition event led to a particular outcome, state, or consequence for the involved entities.
-
B.
acquisitionStatus
chosen
Indicates the current state or outcome of an acquisition process between entities (e.g., pending, completed, failed, or canceled).
-
C.
completedWithDiscoveryOf
Indicates that an action, process, or event was brought to completion as a direct result of a particular discovery.
-
D.
connectsState
Indicates a relationship where one entity serves as a link or conduit between different states, conditions, or statuses of another entity.
-
E.
AOCEstablished
Indicates that an organization or entity was formally founded or brought into existence at a specific time or under specific conditions.
- 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.