Triple
T13452272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Govora spa resort |
E320635
|
entity |
| Predicate | offersTreatmentFor |
P9404
|
FINISHED |
| Object | respiratory diseases |
—
|
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: respiratory diseases | Statement: [Govora spa resort, offersTreatmentFor, respiratory diseases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersTreatmentFor Context triple: [Govora spa resort, offersTreatmentFor, respiratory diseases]
-
A.
offersServiceIn
Indicates that a provider makes a particular service available within a specified location or jurisdiction.
-
B.
offersServiceTo
Indicates that one entity provides or makes a service available for the benefit or use of another entity.
-
C.
offersFeature
chosen
Indicates that one entity provides or makes available a particular feature or capability to another entity.
-
D.
exportTreatment
Indicates the action or process of sending or transferring a treatment (such as a medical, data, or procedural treatment) from one system, location, or context to another for external use or application.
-
E.
offersInformationOn
Indicates that one entity provides or makes available information about another entity or topic.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaefae85481909e6a59797cbb25e7 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:41 p.m.