Triple
T38691925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HDA |
E949288
|
entity |
| Predicate | airlineGroupRole |
P98144
|
FINISHED |
| Object | regional brand of Cathay Pacific Group |
—
|
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: regional brand of Cathay Pacific Group | Statement: [HDA, airlineGroupRole, regional brand of Cathay Pacific Group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airlineGroupRole Context triple: [HDA, airlineGroupRole, regional brand of Cathay Pacific Group]
-
A.
airlineAllianceRole
Indicates the specific role or function an airline holds within an airline alliance.
-
B.
airlineGroupScope
chosen
Indicates that a relationship or action applies specifically within the context or boundaries of a particular airline group.
-
C.
usedByAirlineRole
Indicates that something (such as a resource, system, or process) is utilized by a specific role or position within an airline organization.
-
D.
mergedAirlineRole
Indicates that an airline role has been combined or consolidated with another role as part of an airline merger.
-
E.
associatedAirlineRole
Indicates a relationship where a specific role or position is linked to, or functions within, a particular airline.
- 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_69f76efe16148190befd5dd59c3dfeaa |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.