Triple
T4047252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Couloir |
E84095
|
entity |
| Predicate | reasonForTiming |
P41485
|
FINISHED |
| Object | reduced rockfall when temperatures are lower |
—
|
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: reduced rockfall when temperatures are lower | Statement: [Grand Couloir, reasonForTiming, reduced rockfall when temperatures are lower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForTiming Context triple: [Grand Couloir, reasonForTiming, reduced rockfall when temperatures are lower]
-
A.
reasonForTime
chosen
Indicates that one entity provides the explanation or cause for a particular point or duration of time associated with another entity.
-
B.
commitmentTiming
Indicates the point in time or period relative to an event or agreement when a commitment is made, becomes effective, or is expected to be fulfilled.
-
C.
reasonForExecution
Indicates that one entity specifies the cause, motive, or justification for carrying out the execution of another entity or action.
-
D.
postponementReason
Indicates the reason or cause for which an event, action, or decision has been delayed or rescheduled.
-
E.
time
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
- 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_69aed930bd5c819083e7dcc14fc44f69 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb62593c8190ab8462c4d9cd9d08 |
completed | March 9, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69aef900386481909d04555a9ec9b0e3 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:37 p.m.