Triple
T33819134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevin Patterson |
E866774
|
entity |
| Predicate | holidayDestination |
P21947
|
FINISHED |
| Object | Ibiza |
—
|
NE NERFINISHED |
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: Ibiza | Statement: [Kevin Patterson, holidayDestination, Ibiza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holidayDestination Context triple: [Kevin Patterson, holidayDestination, Ibiza]
-
A.
journeyDestination
chosen
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
-
B.
travelScope
Indicates the extent or range within which travel is allowed, intended, or applicable for an entity or activity.
-
C.
travelZone
Indicates a relationship where an entity is located in, moves within, or is permitted to move within a specified geographic or regulatory area.
-
D.
holidayLocationType
Indicates the type or category of location associated with a holiday or vacation.
-
E.
tourismRegion
Indicates that a place or area is designated or recognized as a tourism region associated with another geographic or administrative 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fff809b881909c0c303f693eb3bc |
completed | May 3, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:46 a.m.