Triple
T28646448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jorsalle |
E725069
|
entity |
| Predicate | commonVisitors |
P34539
|
FINISHED |
| Object | Everest Base Camp trekkers |
—
|
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: Everest Base Camp trekkers | Statement: [Jorsalle, commonVisitors, Everest Base Camp trekkers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonVisitors Context triple: [Jorsalle, commonVisitors, Everest Base Camp trekkers]
-
A.
primaryVisitors
chosen
Indicates that certain entities are the main or most important visitors associated with another entity or context.
-
B.
hasVisitorsFrom
Indicates that an entity receives or has received visitors originating from another specified entity or location.
-
C.
visitorService
Indicates a relationship where a service is provided specifically for or to visitors, such as assistance, information, or support during their visit.
-
D.
receivesVisitorsEspeciallyIn
Indicates that an entity regularly accepts or hosts visitors particularly in a specified place, context, or time period.
-
E.
visitorPractice
Indicates that a visitor engages in or performs a particular practice, activity, or routine.
- 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: April 28, 2026, 4:48 a.m.