Triple
T33712734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chengdu Airlines |
E863784
|
entity |
| Predicate | hasDomesticOperations |
P181694
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Chengdu Airlines, hasDomesticOperations, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDomesticOperations Context triple: [Chengdu Airlines, hasDomesticOperations, yes]
-
A.
hasBusinessOperationsIn
Indicates that a business or organization conducts commercial or operational activities within a specified geographic location or jurisdiction.
-
B.
operatesInternationally
Indicates that the entity conducts activities or business across national borders in multiple countries.
-
C.
hasBaseOfOperations
Indicates that an entity uses a particular location as its primary place of operation or activity.
-
D.
operatesInTerritoriesOutside
Indicates that an entity conducts activities or maintains operations in geographic areas beyond its primary or home territories.
-
E.
hasDomesticServices
Indicates that an entity provides or is associated with services intended for use within a home or domestic setting.
- F. None of above. chosen
Provenance (4 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_69f3498844608190bb8f9b14908d2510 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f7805c25dc8190b9977c561ba15975 |
completed | May 3, 2026, 5:05 p.m. |
Created at: May 1, 2026, 1:43 a.m.