Triple
T7277629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kom–Emine route |
E163068
|
entity |
| Predicate | approximateCompletionTimeOnFoot |
P17474
|
FINISHED |
| Object | about 20–25 days |
—
|
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: about 20–25 days | Statement: [Kom–Emine route, approximateCompletionTimeOnFoot, about 20–25 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateCompletionTimeOnFoot Context triple: [Kom–Emine route, approximateCompletionTimeOnFoot, about 20–25 days]
-
A.
hasApproximateWalkingTimeTo
Indicates that there is an estimated or approximate amount of time it takes to walk from one entity to another.
-
B.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
C.
approximateHikeTimeRoundTrip
Indicates the estimated total time required to complete a hike from the starting point to the destination and back to the start.
-
D.
timeToComplete
chosen
Indicates the duration required for an entity or process to be fully completed.
-
E.
approximateCrossingTime
Indicates an estimated point in time when one entity is expected to cross or intersect another (such as a path, boundary, or trajectory).
- 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_69c6885c5964819085b209701769877f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb8a0b4881908ff27c5a75bd4a95 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76a84a081908d4184c55b728e48 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:59 p.m.