Triple
T2366878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peach Aviation |
E46001
|
entity |
| Predicate | checkInOptions |
P37808
|
FINISHED |
| Object | online check-in |
—
|
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: online check-in | Statement: [Peach Aviation, checkInOptions, online check-in]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: checkInOptions Context triple: [Peach Aviation, checkInOptions, online check-in]
-
A.
checkInPolicy
Indicates the rules or conditions governing when and how an entity is allowed to check in (e.g., arrive, register, or log presence) in relation to another entity or context.
-
B.
checkInTime
Indicates the time at which an entity arrives at and formally registers its presence at a specified place or event.
-
C.
bookingOption
Indicates a selectable arrangement or choice available for making a booking, such as a specific time, package, or set of conditions under which a reservation can be made.
-
D.
hasCheckInSystem
Indicates that an entity uses or is equipped with a system for registering or recording check-ins.
-
E.
requiresCheckIn
Indicates that one entity must perform a check-in action or be checked in as a prerequisite for another entity, event, or process to proceed.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc74b6bdc8190a12b2bcaa2dd7616 |
completed | March 7, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69abc59b88348190a2d6c08f69974117 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc6443c6c8190b932de2abd8eb28f |
completed | March 7, 2026, 6:31 a.m. |
Created at: March 4, 2026, 7:56 p.m.