Triple
T33647679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norse Atlantic ASA |
E862003
|
entity |
| Predicate | fleetTypeOperatedViaSubsidiary |
P165317
|
FINISHED |
| Object | Boeing 787 Dreamliner |
—
|
NE NERFINISHED |
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: Boeing 787 Dreamliner | Statement: [Norse Atlantic ASA, fleetTypeOperatedViaSubsidiary, Boeing 787 Dreamliner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fleetTypeOperatedViaSubsidiary Context triple: [Norse Atlantic ASA, fleetTypeOperatedViaSubsidiary, Boeing 787 Dreamliner]
-
A.
fleetTypeOperated
Indicates that an entity operates or manages a particular type or category of fleet.
-
B.
fleetType
Indicates the category or classification of a fleet to which an entity belongs or with which it is associated.
-
C.
freightSubsidiary
Indicates that one entity is a subsidiary company specifically involved in freight or cargo operations for another entity.
-
D.
usedByAirlineSubsidiaryOf
chosen
Indicates that something (such as an asset, service, or resource) is utilized by an airline that operates as a subsidiary of another airline or parent company.
-
E.
fleetName
Indicates the name assigned to a particular fleet within a system or context.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:42 a.m.