Triple
T27795800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinaya |
E701204
|
entity |
| Predicate | hasClimbingTourismFunction |
P28239
|
FINISHED |
| Object | gateway village for Mount Illimani |
—
|
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: gateway village for Mount Illimani | Statement: [Pinaya, hasClimbingTourismFunction, gateway village for Mount Illimani]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimbingTourismFunction Context triple: [Pinaya, hasClimbingTourismFunction, gateway village for Mount Illimani]
-
A.
hasClimbingActivity
Indicates that an entity engages in or is associated with a climbing-related activity.
-
B.
hasClimbingTrail
Indicates that a location or area includes or provides access to a designated climbing trail.
-
C.
hasClimbs
Indicates that one entity performs or is associated with climbing activity on another entity (such as a route, structure, or surface).
-
D.
isClimbingDestination
chosen
Indicates that a location serves as a target or goal for a climbing activity or route.
-
E.
hasClimbingInterest
Indicates that an entity has an interest in or enthusiasm for climbing activities.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 27, 2026, 5:31 p.m.