Triple
T35670436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ausangate |
E1030698
|
entity |
| Predicate | isClimbedSince |
P183598
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Ausangate, isClimbedSince, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isClimbedSince Context triple: [Ausangate, isClimbedSince, 20th century]
-
A.
isClimbedToReach
Indicates that an entity ascends or climbs another entity in order to reach a target or destination.
-
B.
isClimbedIn
Indicates that an entity (typically a person or animal) ascends or climbs while being located within or inside another entity (such as a structure, vehicle, or environment).
-
C.
isClimbedAllYear
Indicates that the subject is climbed continuously or is suitable for climbing throughout the entire year, without a specific season.
-
D.
hasClimbFrom
Indicates a relationship where one location or object serves as the starting point from which a climb or ascent to another location or object begins.
-
E.
hasClimb
Indicates that an entity performs or is capable of performing a climbing action on or over another entity or surface.
- F. None of above. chosen
Provenance (4 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a01efcc08190bba489a9099b8684 |
completed | May 3, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79f477c4c8190a35cb6d87b1dcbd1 |
completed | May 3, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:05 p.m.