Triple
T31474644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cahul |
E802957
|
entity |
| Predicate | isSpaDestination |
P160255
|
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: [Cahul, isSpaDestination, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSpaDestination Context triple: [Cahul, isSpaDestination, true]
-
A.
isSpaTown
chosen
Indicates that a place is recognized as a spa town, i.e., a town known for its spa facilities or therapeutic mineral springs.
-
B.
isResortDestinationFor
Indicates that a place serves as a resort destination specifically intended for or frequented by a particular person, group, or entity.
-
C.
isSpaTownOf
Indicates that a place is recognized as a spa town belonging to, or located within the jurisdiction of, a specified larger administrative area or region.
-
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.
isTouristDestination
Indicates that a place is recognized as a location people commonly visit for leisure, sightseeing, or travel.
- 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_69f348c9477c8190bc0a21f6d482d2fc |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:28 p.m.