Triple
T24019394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camp IV (Everest Northeast Ridge) |
E594772
|
entity |
| Predicate | timeSpent |
P17474
|
FINISHED |
| Object | minimized due to altitude risks |
—
|
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: minimized due to altitude risks | Statement: [Camp IV (Everest Northeast Ridge), timeSpent, minimized due to altitude risks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSpent Context triple: [Camp IV (Everest Northeast Ridge), timeSpent, minimized due to altitude risks]
-
A.
spentTimeIn
Indicates that an entity has spent a certain amount or period of time in a particular place or context.
-
B.
endTimeDetail
Indicates the specific or refined information about when an event, action, or state concludes.
-
C.
time
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
-
D.
timeToComplete
chosen
Indicates the duration required for an entity or process to be fully completed.
-
E.
timeRecorded
Indicates that a specific point or period in time has been captured and stored as associated with an event, action, or state.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d5a925208190badd075519a0f4b6 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:42 p.m.