Triple
T32625917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juneyao Group |
E834055
|
entity |
| Predicate | hasSubsidiaryInIndustry |
P158516
|
FINISHED |
| Object | airline industry |
—
|
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: airline industry | Statement: [Juneyao Group, hasSubsidiaryInIndustry, airline industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubsidiaryInIndustry Context triple: [Juneyao Group, hasSubsidiaryInIndustry, airline industry]
-
A.
hasSubsidiariesIn
Indicates that an entity has subsidiary companies or organizations operating or registered in a specified location or jurisdiction.
-
B.
subsidiaryIndustry
chosen
Indicates that a subsidiary company operates within or is associated with a particular industry sector.
-
C.
hasSubsidiaryBusiness
Indicates that one business entity owns or controls another business entity as its subsidiary.
-
D.
hasParentCompanyIndustry
Indicates that an entity’s parent company operates in, or is associated with, a specified industry.
-
E.
hasSubsidiaryLabel
Indicates that one entity is identified as a subsidiary or subordinate organization of another entity.
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff1f3f94fc819095955299f50ab4ce |
completed | May 9, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69ff1ea47748819082f63d9b9d9c3e65 |
completed | May 9, 2026, 11:46 a.m. |
Created at: May 1, 2026, 1:06 a.m.