Triple
T27200098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T4 |
E683711
|
entity |
| Predicate | hasTypeOfCarrierFocus |
P5323
|
FINISHED |
| Object | low-cost airlines |
—
|
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: low-cost airlines | Statement: [T4, hasTypeOfCarrierFocus, low-cost airlines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfCarrierFocus Context triple: [T4, hasTypeOfCarrierFocus, low-cost airlines]
-
A.
hasCargoFocus
Indicates that an entity’s primary attention, resources, or functionality are directed toward handling or managing cargo.
-
B.
isMajorCarrierOf
Indicates that one entity serves as the primary or principal transporter or conveyor of another entity (such as goods, signals, or passengers).
-
C.
hasTransitFocus
chosen
Indicates that something is oriented toward, prioritizes, or is primarily concerned with transit or transportation services.
-
D.
usesAsCarrier
Indicates that one entity employs another entity as a carrier or medium for transporting or conveying something.
-
E.
hasPetTypeFocus
Indicates that an entity’s primary focus or concern is on a specific type or category of pet.
- 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_69eefad1fd5c8190a4a46ea6afe58bfa |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 27, 2026, 9:36 a.m.