Triple
T9101211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pegas Touristik |
E218158
|
entity |
| Predicate | typicalDestinationType |
P1769
|
FINISHED |
| Object | beach resorts |
—
|
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: beach resorts | Statement: [Pegas Touristik, typicalDestinationType, beach resorts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDestinationType Context triple: [Pegas Touristik, typicalDestinationType, beach resorts]
-
A.
notableDestinationType
Indicates the general category or type of destination for which something is considered notable.
-
B.
servesDestinationType
Indicates that an entity provides service to, or is intended for use with, a specific type or category of destination.
-
C.
typicalJourneyPurpose
Indicates the usual or most common reason or objective for which an entity undertakes a journey.
-
D.
typicalPickupType
Indicates the usual or standard method by which an item or order is collected or picked up.
-
E.
tourismType
chosen
Indicates the specific category or kind of tourism activity or experience associated with an entity.
- 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_69ca83d9844081908e561e367fda6d45 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc971435d08190b5007ed44ac0a364 |
completed | April 1, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:15 p.m.