Triple
T37875190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Premia |
E944699
|
entity |
| Predicate | offersMobileCheckIn |
P185249
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Air Premia, offersMobileCheckIn, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersMobileCheckIn Context triple: [Air Premia, offersMobileCheckIn, true]
-
A.
offersMobileAppOrdering
Indicates that an entity provides the ability for customers to place orders through a mobile application.
-
B.
hasOnlineCheckIn
chosen
Indicates that an entity offers or supports the ability to check in via an online or digital platform.
-
C.
hasMobileOrder
Indicates that an entity has placed or is associated with a mobile-based order.
-
D.
hasCheckInSystem
Indicates that an entity uses or is equipped with a system for registering or recording check-ins.
-
E.
hasMobileKey
Indicates that an entity possesses or is associated with a mobile-based digital key used for access or authentication.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
Created at: May 3, 2026, 4:19 p.m.