Triple
T27019412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Himalaya Airlines |
E680622
|
entity |
| Predicate | hasHeadquartersAddressCity |
P60125
|
FINISHED |
| Object | Kathmandu |
—
|
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: Kathmandu | Statement: [Himalaya Airlines, hasHeadquartersAddressCity, Kathmandu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeadquartersAddressCity Context triple: [Himalaya Airlines, hasHeadquartersAddressCity, Kathmandu]
-
A.
hasHeadOfficeCity
chosen
Indicates that an organization’s main or central administrative office is located in a particular city.
-
B.
issuerHeadquartersAddressCity
Indicates the city where the issuer’s headquarters address is located.
-
C.
hasOrganizationHeadquarters
Indicates that an organization’s main administrative or operational center is located at a specific place.
-
D.
laterCompanyHeadquartersCity
Indicates that the specified city is the location of a company’s headquarters during a later period in time, following an earlier headquarters location.
-
E.
sponsorHeadquartersCity
Indicates the city where the sponsoring organization’s main headquarters is located.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 7:07 a.m.