Triple
T91564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JetBlue Airways |
E1838
|
entity |
| Predicate | MintServiceType |
P849
|
FINISHED |
| Object | lie-flat seats on select routes |
—
|
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: lie-flat seats on select routes | Statement: [JetBlue Airways, MintServiceType, lie-flat seats on select routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MintServiceType Context triple: [JetBlue Airways, MintServiceType, lie-flat seats on select routes]
-
A.
hasServiceType
chosen
Indicates that an entity is associated with or categorized by a particular type of service.
-
B.
typeOfSupport
Indicates the kind or category of assistance, help, or backing provided in a given context.
-
C.
servesMode
Indicates that one entity provides or operates in a particular manner, method, or mode in relation to another entity or context.
-
D.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
E.
operationType
Indicates the specific kind of operation or action being performed or recorded in the relationship between entities.
- 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_69a24d1a97dc819094e6c021fe9b05a7 |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a2512ef600819084d3c627f0d534f4 |
completed | Feb. 28, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69a24eb9a5ac8190b1d1300e8c4e3606 |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:07 a.m.