Triple
T29756879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lacco Ameno |
E753052
|
entity |
| Predicate | isThermalResort |
P167850
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lacco Ameno, isThermalResort, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isThermalResort Context triple: [Lacco Ameno, isThermalResort, true]
-
A.
isResortTown
Indicates that a town functions primarily as a resort destination, typically focused on tourism, leisure, and vacation activities.
-
B.
isResortDestinationFor
Indicates that a place serves as a resort destination specifically intended for or frequented by a particular person, group, or entity.
-
C.
isResortCityOn
Indicates that a city, characterized as a resort destination, is located on or directly adjacent to a specified geographic feature (such as a coast, lake, or mountain range).
-
D.
isResortOf
Indicates that a location or facility functions as a resort associated with, belonging to, or serving a particular entity (such as a city, region, or organization).
-
E.
isFourSeasonResort
Indicates that a resort operates and is available to guests throughout all four seasons of the year.
- 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f673cbcbac819098e3b944b6fcfd1e |
completed | May 2, 2026, 9:59 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 28, 2026, 7:57 p.m.