Triple
T20881574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TS |
E514163
|
entity |
| Predicate | airlinePrimaryFocus |
P4366
|
FINISHED |
| Object | vacation travel |
—
|
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: vacation travel | Statement: [TS, airlinePrimaryFocus, vacation travel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airlinePrimaryFocus Context triple: [TS, airlinePrimaryFocus, vacation travel]
-
A.
mainAirlineFocus
chosen
Indicates that an airline is the primary or central focus of attention, operations, or analysis in a given context.
-
B.
airline
Indicates that an entity operates as a commercial air transport carrier providing flight services between locations.
-
C.
airlineCategory
Indicates the classification or type of an airline within a defined categorization system (e.g., full-service, low-cost, regional).
-
D.
airlineType
Indicates the classification or category of an airline based on its operational or service characteristics.
-
E.
airlineContext
Indicates a relationship, situation, or action that specifically occurs within or is constrained by an airline-related context (such as flights, carriers, or air travel operations).
- 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c67a33548190b0f5ba58b001d387 |
completed | April 21, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:46 p.m.