Triple
T8709875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allegiant Air |
E206746
|
entity |
| Predicate | notableDestinationType |
P84669
|
FINISHED |
| Object | vacation destinations |
—
|
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 destinations | Statement: [Allegiant Air, notableDestinationType, vacation destinations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDestinationType Context triple: [Allegiant Air, notableDestinationType, vacation destinations]
-
A.
notableDestination
Indicates that a location is recognized as a significant or prominent place that people commonly travel to or aim to visit.
-
B.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
C.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
D.
notableLocationFeatured
Indicates that a particular location is prominently highlighted or showcased in relation to the subject.
-
E.
notableResort
Indicates that a location functions as a resort that is recognized for its significance, prominence, or special reputation.
- 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_69ca835645e881908f00e3c8b51da81d |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5c3034708190b895eaf890d62198 |
completed | March 31, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc582412f48190ae819965bfb0e75d |
completed | March 31, 2026, 11:26 p.m. |
Created at: March 30, 2026, 6:35 p.m.