Triple
T4498470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Pacific |
E100756
|
entity |
| Predicate | rebrandingAnnounced |
P21766
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Air Pacific, rebrandingAnnounced, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebrandingAnnounced Context triple: [Air Pacific, rebrandingAnnounced, 2012]
-
A.
renamingAnnouncedBy
Indicates that an entity’s change of name has been publicly announced or made known by another specified entity.
-
B.
brandingIntroduced
chosen
Indicates that a particular branding or brand identity has been newly introduced or brought into use for an entity.
-
C.
brandingChangeDate
Indicates the date on which a change in branding (such as name, logo, or visual identity) took effect.
-
D.
focusAfterRebrand
Indicates that an entity’s primary emphasis, strategy, or positioning is considered in the period following a rebranding effort.
-
E.
brandingNote
Indicates that an entity has an associated note or comment specifically about its branding, such as style, usage, or presentation guidelines.
- 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_69bd43cdf15081909a4fa2585ff63b3e |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56c065e88190934eb0b1632d79bb |
completed | March 20, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1 p.m.