Triple
T26955772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cayo Ensenachos |
E678898
|
entity |
| Predicate | hasMainAccommodation |
P181081
|
FINISHED |
| Object | Iberostar Selection Ensenachos |
—
|
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: Iberostar Selection Ensenachos | Statement: [Cayo Ensenachos, hasMainAccommodation, Iberostar Selection Ensenachos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainAccommodation Context triple: [Cayo Ensenachos, hasMainAccommodation, Iberostar Selection Ensenachos]
-
A.
hasAccommodation
Indicates that an entity provides, owns, or is associated with a place for someone to stay or live.
-
B.
hasAccommodations
chosen
Indicates that one entity provides, contains, or offers lodging, facilities, or special arrangements for another entity.
-
C.
hasTouristAccommodationType
Indicates that an entity provides or is classified by a specific type or category of tourist accommodation.
-
D.
hasGuestHouse
Indicates that one entity owns, includes, or is associated with a guest house in relation to another entity.
-
E.
sleepingAccommodation
Indicates that one entity serves as a place or facility where another entity can sleep or stay overnight.
- 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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: April 27, 2026, 6:27 a.m.