Triple
T475362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JBLU |
E9048
|
entity |
| Predicate | underlyingBusinessType |
P6749
|
FINISHED |
| Object | public company |
—
|
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: public company | Statement: [JBLU, underlyingBusinessType, public company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingBusinessType Context triple: [JBLU, underlyingBusinessType, public company]
-
A.
underlyingCompany
Indicates that one entity serves as the fundamental or base company upon which another entity (such as a product, instrument, or structure) is built, derived, or dependent.
-
B.
industryOfUnderlyingCompany
Indicates the industry sector in which the underlying company associated with this entity operates.
-
C.
underlyingCompanyBusinessFocus
chosen
Indicates the primary industry, sector, or type of business activity that the underlying company is focused on.
-
D.
laterBusinessBase
Indicates that one business entity serves as the subsequent or successor base of operations relative to another business entity.
-
E.
settlementType
Indicates the specific kind or category of human settlement an entity represents, such as a city, village, town, or hamlet.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f03b5e5081908ee3dba9d19a6871 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edeed31881908cf43beed410572d |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.