Triple
T32444801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kunde Hospital |
E829112
|
entity |
| Predicate | nearTouristDestination |
P3449
|
FINISHED |
| Object | Everest Base Camp trekking route |
—
|
NE NERFINISHED |
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: Everest Base Camp trekking route | Statement: [Kunde Hospital, nearTouristDestination, Everest Base Camp trekking route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearTouristDestination Context triple: [Kunde Hospital, nearTouristDestination, Everest Base Camp trekking route]
-
A.
nearbyRoyalSite
Indicates that one place or object is located close to a site associated with royalty, such as a palace, castle, or royal residence.
-
B.
typicalNearbyLandmarks
Indicates that certain landmarks are commonly found in the vicinity of a given place or location.
-
C.
nearbyWorldHeritageSite
Indicates that one entity is located close to, or in the immediate vicinity of, a designated World Heritage Site.
-
D.
touristAttractionIn
Indicates that a place functions as a tourist attraction located within a specified geographic area or entity.
-
E.
hasAttractionNearby
chosen
Indicates that one entity is located close to another entity that serves as an attraction or point of interest.
- 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2e5a0ec819098203f775adb5d03 |
completed | May 3, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:55 a.m.