Triple
T26440208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiffin Top |
E665065
|
entity |
| Predicate | approxTrekTimeFromNainital |
P178267
|
FINISHED |
| Object | about 1 to 2 hours |
—
|
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 1 to 2 hours | Statement: [Tiffin Top, approxTrekTimeFromNainital, about 1 to 2 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approxTrekTimeFromNainital Context triple: [Tiffin Top, approxTrekTimeFromNainital, about 1 to 2 hours]
-
A.
distanceToNainital
Indicates the spatial distance between a given location or entity and the place Nainital.
-
B.
approxTrekDistanceFromGangotri
Indicates the approximate trekking distance measured from Gangotri to another location or point of interest.
-
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.
timeFromLukla
Indicates the amount of time required to travel from Lukla to the referenced location or event.
-
E.
distanceToSrinagar_km
Indicates the physical distance, measured in kilometers, between a given place or entity and the city of Srinagar.
- F. None of above. chosen
Provenance (4 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_69ee883c851881909e2ab04efbb3c5fe |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: April 26, 2026, 11:57 p.m.