Triple
T28993321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Playa Colora |
E736085
|
entity |
| Predicate | bestVisitedAs |
P166096
|
FINISHED |
| Object | day trip destination |
—
|
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: day trip destination | Statement: [Playa Colora, bestVisitedAs, day trip destination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestVisitedAs Context triple: [Playa Colora, bestVisitedAs, day trip destination]
-
A.
bestVisitedBy
Indicates that an entity is most suitably or optimally accessed, experienced, or reached by using a particular mode, route, or means of visiting.
-
B.
bestVisitedAt
Indicates the optimal time or conditions under which a place or entity should be visited.
-
C.
isMostVisitedOf
Indicates that an entity has the highest number of visits compared to all other entities in a specified group or context.
-
D.
wasFirstVisitedBy
Indicates that a particular entity was initially reached, discovered, or visited by another specified entity before any others.
-
E.
mostVisitedPartOf
Indicates that one entity is the part or region of another entity that receives the highest number of visits or traffic compared to its other parts.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65f7f067081909057e9c6e1fd0bdd |
completed | May 2, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65b136b30819090cf59fb772f35f1 |
completed | May 2, 2026, 8:14 p.m. |
Created at: April 28, 2026, 9:28 a.m.