Triple
T11382296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dubrovnik Airport |
E269624
|
entity |
| Predicate | primaryPassengerPurpose |
P79244
|
FINISHED |
| Object | leisure tourism |
—
|
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: leisure tourism | Statement: [Dubrovnik Airport, primaryPassengerPurpose, leisure tourism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryPassengerPurpose Context triple: [Dubrovnik Airport, primaryPassengerPurpose, leisure tourism]
-
A.
typicalJourneyPurpose
Indicates the usual or most common reason or objective for which an entity undertakes a journey.
-
B.
spouseTravelPurpose
Indicates that the purpose of a spouse’s travel is specified in relation to another entity or event.
-
C.
sunJourneyPurpose
Indicates the purpose or intended goal behind a sun-related journey or movement.
-
D.
primaryIntent
Indicates the main purpose, goal, or motivation underlying an action, event, or relationship among entities.
-
E.
flightPurpose
chosen
Indicates the reason or intended purpose for which a particular flight is being taken or operated.
- 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_69d6aacca1048190b39dbbc2174616fa |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d800160a1c81909d115bf89fe54a49 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e70b228c8190b87f5101fd683788 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.