Triple
T31938823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Göd |
E815467
|
entity |
| Predicate | hasLeisureFacilityType |
P6792
|
FINISHED |
| Object | thermal spa |
—
|
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: thermal spa | Statement: [Göd, hasLeisureFacilityType, thermal spa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeisureFacilityType Context triple: [Göd, hasLeisureFacilityType, thermal spa]
-
A.
isRecreationalFacility
Indicates that the subject entity functions as a place or installation intended for leisure, sports, or other recreational activities.
-
B.
hasRecreationFacility
chosen
Indicates that one entity provides, contains, or is equipped with a recreational facility for use by another entity or by the public.
-
C.
hasCivicAmenity
Indicates that an entity possesses, provides, or is associated with a public facility or service intended for community use.
-
D.
hasCulturalFacilityType
Indicates that an entity has or is associated with a specific type of cultural facility (such as a museum, theater, or gallery).
-
E.
isRecreationFacilityType
Indicates that one entity is classified as a specific type or category of recreation facility in relation to another entity.
- 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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 1, 2026, 12:05 a.m.