Triple
T37819993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dawn Wall route |
E942881
|
entity |
| Predicate | projectedForYearsBy |
P189543
|
FINISHED |
| Object | Tommy Caldwell |
—
|
NE NERFINISHED |
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: Tommy Caldwell | Statement: [Dawn Wall route, projectedForYearsBy, Tommy Caldwell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectedForYearsBy Context triple: [Dawn Wall route, projectedForYearsBy, Tommy Caldwell]
-
A.
typicalProjectionYear
Indicates the year that is typically used as the reference point for projecting or forecasting values in a given context.
-
B.
appliesInYears
Indicates that something (such as a rule, condition, or effect) is valid, relevant, or in force during specific years.
-
C.
planningHorizonYears
Indicates the number of years into the future over which planning or forecasting is intended to be carried out.
-
D.
energyProjectionType
Indicates the specific form or mode in which energy is projected or emitted in a given interaction or event.
-
E.
coversYearsTo
Indicates a temporal relationship where one entity spans, includes, or extends up to a specified year or range of years represented by the other entity.
- 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_69f76ee987588190906506e759be5db3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:19 p.m.