Triple
T38042630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dihedral Wall, El Capitan |
E949529
|
entity |
| Predicate | notableClimberAssociated |
P207570
|
FINISHED |
| Object | Chuck Pratt |
E278664
|
NE 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: Chuck Pratt | Statement: [Dihedral Wall, El Capitan, notableClimberAssociated, Chuck Pratt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableClimberAssociated Context triple: [Dihedral Wall, El Capitan, notableClimberAssociated, Chuck Pratt]
-
A.
includedClimber
Indicates that a climber is part of, or counted within, a specified group, set, or collection of climbers.
-
B.
associatedWithMountain
Indicates a relationship in which something has a connection, link, or relevance to a mountain.
-
C.
notableClimbs
Indicates that the subject has completed or is associated with particularly significant or well-known climbing routes or ascents.
-
D.
alsoClimbed
Indicates that one entity climbed something that another specified entity also climbed.
-
E.
hasFirstRecordedAscents
Indicates that the subject is associated with the earliest known successful ascents of the specified object(s), typically in a mountaineering or climbing context.
- F. None of above. chosen
Provenance (5 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a415d30d0908190aa8f79c12876dae2 |
completed | June 28, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037df009f4819082e04683e6e8a106 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:20 p.m.