Triple
T37284326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starlux Airlines |
E925488
|
entity |
| Predicate | cityServedAsHub |
P178557
|
FINISHED |
| Object | Taipei |
—
|
NE NERFINISHED |
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: Taipei | Statement: [Starlux Airlines, cityServedAsHub, Taipei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityServedAsHub Context triple: [Starlux Airlines, cityServedAsHub, Taipei]
-
A.
cityServedFromHub
Indicates that a particular city is served or connected via transportation routes originating from a specified hub.
-
B.
alternativeCityServed
Indicates that one city functions as an alternative service location for another city, typically in contexts like transportation or logistics.
-
C.
associatedCityServed
chosen
Indicates that there is a relationship where a service, facility, or entity is linked to and serves a particular city.
-
D.
cityServedType
Indicates the type or category of city that is served by a given entity (such as a facility, service, or infrastructure).
-
E.
modernCityServed
Indicates that a modern city receives services, support, or functions (such as transportation, utilities, or administration) from a specified provider or infrastructure.
- 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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.