Triple
T17858651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Coochin |
E446005
|
entity |
| Predicate | hasApproximateAscentTime |
P96776
|
FINISHED |
| Object | 30 to 45 minutes |
—
|
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: 30 to 45 minutes | Statement: [Mount Coochin, hasApproximateAscentTime, 30 to 45 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateAscentTime Context triple: [Mount Coochin, hasApproximateAscentTime, 30 to 45 minutes]
-
A.
approximateAscentTime
chosen
Indicates the estimated amount of time required for an entity to ascend or climb to a specified point or elevation.
-
B.
approximateDescentTime
Indicates an estimated or calculated time at which a descent event is expected to occur.
-
C.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
D.
hasApproximateDuration
Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
-
E.
approximateAscentTimeFromRefuge
Indicates the estimated amount of time required to ascend from a specified refuge to a target point or destination.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4978e68ec8190a4306f7b7bb058d7 |
completed | April 19, 2026, 8:51 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e6d2e88190ad9ef9f8a99f13e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:17 a.m.