Triple
T5599673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Tebulosmta |
E147085
|
entity |
| Predicate | hasFirstAscent |
P1320
|
FINISHED |
| Object | unknown |
—
|
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: unknown | Statement: [Mount Tebulosmta, hasFirstAscent, unknown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstAscent Context triple: [Mount Tebulosmta, hasFirstAscent, unknown]
-
A.
firstAscent
chosen
Indicates that an entity represents the earliest known successful ascent or climb of a particular route, peak, or feature.
-
B.
firstAscentBy
Indicates the person or party that first successfully ascended or climbed a particular route, peak, or feature.
-
C.
hasFirstRecordedAscent
Indicates that a particular ascent is the earliest known or documented successful climb of a specific route, peak, or climbing objective.
-
D.
usualFirstAscentBy
Indicates that the referenced entity is the person or party who is typically credited with making the first ascent of a particular route, peak, or climbing objective.
-
E.
firstAscentFrom
Indicates the starting location or route from which the first successful ascent of something (typically a peak or climb) was made.
- 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_69c009043d648190a7af89698ccf1e3e |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020d936dc8190a2e599f1df9fdd91 |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1890ec8190b9e6fa488792e4d4 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:38 p.m.