Triple
T10412375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CA |
E245422
|
entity |
| Predicate | airlineLegalForm |
P94002
|
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: [CA, airlineLegalForm, public company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airlineLegalForm Context triple: [CA, airlineLegalForm, public company]
-
A.
airlineLegalName
Indicates the official registered legal name under which an airline is formally incorporated and operates.
-
B.
airlineType
Indicates the classification or category of an airline based on its operational or service characteristics.
-
C.
representsAirline
Indicates that one entity serves as the airline associated with, operating, or branding the other entity (such as a flight, route, or service).
-
D.
airlineOwnershipType
Indicates the type or nature of ownership relationship that exists between an airline and its owning entity.
-
E.
airlineRegulatoryAuthority
Indicates that one entity serves as the official regulatory authority overseeing and governing the operations of an airline or airlines.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea0e17f081908fb16425f65e5808 |
completed | April 7, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb6f160819090040644a12395ec |
completed | April 7, 2026, 10:43 a.m. |
| PDg | Predicate description generation | batch_69d4e91ce2008190af252c140370b7f2 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:10 p.m.