Triple
T2248159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HK Express |
E49553
|
entity |
| Predicate | focusMarket |
P28886
|
FINISHED |
| Object | budget travel |
—
|
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: budget travel | Statement: [HK Express, focusMarket, budget travel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusMarket Context triple: [HK Express, focusMarket, budget travel]
-
A.
coreMarket
chosen
Indicates that an entity serves as the primary or most important market for another entity’s products, services, or activities.
-
B.
relatedMarket
Indicates that two markets are connected or associated, such that activity, conditions, or changes in one market are relevant to or influence the other.
-
C.
peakMarketShare
Indicates the highest proportion of total market sales or customers that an entity has achieved over a specified period.
-
D.
focusType
Indicates the specific kind or category of focus or attention that is being applied to or associated with an entity or interaction.
-
E.
market
Indicates the act of promoting, advertising, or selling a product, service, or idea to potential buyers or target audiences.
- 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_69a88aa979788190ad6500f1d8eee2fc |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0ed5c38819080b45ea398fb59f2 |
completed | March 7, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69abbdb160248190aa75b38f11ad8602 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.