Triple
T27842124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jetstar Pacific Airlines |
E703710
|
entity |
| Predicate | dateRebrandedAsJetstarPacific |
P163402
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [Jetstar Pacific Airlines, dateRebrandedAsJetstarPacific, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateRebrandedAsJetstarPacific Context triple: [Jetstar Pacific Airlines, dateRebrandedAsJetstarPacific, 2008]
-
A.
dateRenamedToFlybe
Indicates that the entity’s date corresponds to the point in time when it was renamed to Flybe.
-
B.
airlineFormerName
Indicates that an airline previously operated under a different name, specifying its former official designation.
-
C.
airlineAllianceJoinDate
Indicates the date on which an airline became a member of a particular airline alliance.
-
D.
successorAirline
Indicates that one airline has taken over, replaced, or continued the operations of another airline as its successor.
-
E.
airlineBrand
Indicates that one entity functions as the commercial airline brand associated with, or operating under, another entity.
- 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f638d75ba48190bfd2a602f4c5361a |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6359d46b88190922dd7de508e3b0e |
completed | May 2, 2026, 5:34 p.m. |
Created at: April 27, 2026, 6:04 p.m.