Triple
T32758824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Gayong |
E837699
|
entity |
| Predicate | standardAscentTime |
P96776
|
FINISHED |
| Object | 2–3 days for Korbu–Gayong traverse |
—
|
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: 2–3 days for Korbu–Gayong traverse | Statement: [Mount Gayong, standardAscentTime, 2–3 days for Korbu–Gayong traverse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardAscentTime Context triple: [Mount Gayong, standardAscentTime, 2–3 days for Korbu–Gayong traverse]
-
A.
approximateAscentTime
chosen
Indicates the estimated amount of time required for an entity to ascend or climb to a specified point or elevation.
-
B.
ascentDate
Indicates the date on which an ascent, climb, or upward journey took place.
-
C.
ascentStageImpactDate
Indicates the calendar date on which an ascent stage impacts a surface or target body.
-
D.
standardTimeType
Indicates that a time value is expressed using a particular standard or conventional time format or classification.
-
E.
typicalAscentStartPoint
Indicates the usual or most common location from which an ascent or climb is begun.
- 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_69f34937f97c8190b7f84bea045df3ae |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 1, 2026, 1:13 a.m.