Triple
T20815948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balatonfüred District |
E512436
|
entity |
| Predicate | hasResortCharacter |
P141936
|
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: [Balatonfüred District, hasResortCharacter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResortCharacter Context triple: [Balatonfüred District, hasResortCharacter, true]
-
A.
hasResortType
Indicates that an entity (such as a resort or accommodation) is associated with a specific category or type of resort (e.g., beach resort, ski resort, spa resort).
-
B.
hasResortHotel
Indicates that one entity owns, includes, or is associated with a resort hotel as part of its facilities or offerings.
-
C.
hasResortAccessTo
Indicates that one entity is permitted to use, enter, or benefit from the facilities or services of a particular resort.
-
D.
hasResortBrand
Indicates that a resort is associated with, operated by, or marketed under a specific resort brand.
-
E.
hasResortCenter
Indicates that an entity includes or is associated with a resort facility serving as a central location for leisure or vacation activities.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2f3473c81908c43a2ec242b1acd |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:41 p.m.