Triple
T13961739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fačkovské sedlo |
E335809
|
entity |
| Predicate | hasRestaurantFacilities |
P55802
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Fačkovské sedlo, hasRestaurantFacilities, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRestaurantFacilities Context triple: [Fačkovské sedlo, hasRestaurantFacilities, yes]
-
A.
hasFacilities
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
-
B.
hasGoodsFacilities
Indicates that a location or entity is equipped with facilities for handling, storing, or processing goods or cargo.
-
C.
hasDiningFeature
chosen
Indicates that something possesses a specific characteristic, amenity, or attribute related to dining.
-
D.
hasMaintenanceFacilities
Indicates that one entity provides or contains facilities where the other entity can be serviced, repaired, or maintained.
-
E.
hasBackstageFacilities
Indicates that a venue or location provides backstage areas and related facilities for performers or staff.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e7c73d48190b8e02971b5a8ed5f |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:18 p.m.