Triple
T34132629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Salvo |
E875468
|
entity |
| Predicate | hasBeachResorts |
P185685
|
FINISHED |
| Object | lidos and bathing establishments |
—
|
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: lidos and bathing establishments | Statement: [San Salvo, hasBeachResorts, lidos and bathing establishments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeachResorts Context triple: [San Salvo, hasBeachResorts, lidos and bathing establishments]
-
A.
hasBeach
Indicates that one entity possesses, includes, or is characterized by a beach as part of its features or environment.
-
B.
hasBeachDestination
Indicates that a place is a destination characterized by having a beach suitable for visits or recreation.
-
C.
hasBeachResortStatus
Indicates that an entity holds the designation or classification of being a beach resort.
-
D.
hasBeachNearby
Indicates that one location is situated close enough to another location to have convenient access to a beach.
-
E.
hasCoastlineResort
Indicates that a geographic area or location contains a resort situated along its coastline.
- 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c29cf36481908e472d4dcb5573b9 |
completed | May 3, 2026, 9:48 p.m. |
Created at: May 1, 2026, 1:53 a.m.