Triple
T2907569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WestJet |
E63601
|
entity |
| Predicate | previousLegalForm |
P42670
|
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: [WestJet, previousLegalForm, public company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousLegalForm Context triple: [WestJet, previousLegalForm, public company]
-
A.
legalForm
Indicates the specific legal structure or organizational type under which an entity is formally constituted and recognized by law.
-
B.
legalPredecessorDocument
Indicates that one document is legally recognized as preceding and providing the formal basis or prior version for another document.
-
C.
legalPersonality
Indicates that an entity possesses recognized legal status, enabling it to hold rights, bear obligations, and act as a subject under the law.
-
D.
hasUnderlyingCompanyLegalForm
Indicates that an entity is associated with, or governed by, a specific underlying legal form of a company.
-
E.
legalEstablishment
Indicates that an entity has been formally created, recognized, or brought into existence according to legal rules or procedures.
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe0d1dcf881909b3ae58d7cdfd9cd |
completed | March 7, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69abdd19bac881908f047d616aca8438 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abdd96670c8190b727f9ac27dadf67 |
completed | March 7, 2026, 8:11 a.m. |
Created at: March 6, 2026, 10:11 p.m.