Triple
T22104589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tapovan |
E546252
|
entity |
| Predicate | typicalTrekDurationFromGangotri |
P72407
|
FINISHED |
| Object | 4–6 days round trip |
—
|
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: 4–6 days round trip | Statement: [Tapovan, typicalTrekDurationFromGangotri, 4–6 days round trip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTrekDurationFromGangotri Context triple: [Tapovan, typicalTrekDurationFromGangotri, 4–6 days round trip]
-
A.
approxTrekDistanceFromGangotri
Indicates the approximate trekking distance measured from Gangotri to another location or point of interest.
-
B.
trekDistanceToYamunotri
Indicates the distance covered while trekking from a starting point to the destination Yamunotri.
-
C.
recommendedTimeToHike
Indicates the suggested or optimal time period during which one should undertake a particular hike.
-
D.
dayOfTrek
Indicates the specific day or stage within a multi-day trek on which an event, action, or condition occurs.
-
E.
typicalTourDuration
chosen
Indicates the usual length of time that a tour normally takes to complete.
- 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_69e11e378dc08190896d6a51597afd5a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1291815f88190a6eaf73e444dc1c2 |
completed | April 28, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:30 p.m.