Triple
T13151039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kibo summit crater |
E312465
|
entity |
| Predicate | summitActivity |
P77841
|
FINISHED |
| Object | high-altitude trekking |
—
|
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: high-altitude trekking | Statement: [Kibo summit crater, summitActivity, high-altitude trekking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitActivity Context triple: [Kibo summit crater, summitActivity, high-altitude trekking]
-
A.
summitView
Indicates a vantage point or perspective that is obtained from the top or highest point of something, such as a mountain or structure.
-
B.
summitStatus
Indicates the current state or outcome of a summit event, such as whether it is planned, ongoing, completed, or canceled.
-
C.
summitPractice
chosen
Indicates that an entity engages in or is associated with a practice, activity, or event related to a summit (such as a high-level meeting or peak-focused endeavor).
-
D.
summitUsedBy
Indicates that a particular summit is utilized or accessed by a specified entity (such as a person, group, or organization).
-
E.
holdsSummit
Indicates that an entity organizes and conducts a formal summit meeting or conference with others.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:11 p.m.