Triple
T8159187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annapurna Circuit |
E190530
|
entity |
| Predicate | typicalDurationRange |
P7618
|
FINISHED |
| Object | 12–21 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: 12–21 days | Statement: [Annapurna Circuit, typicalDurationRange, 12–21 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDurationRange Context triple: [Annapurna Circuit, typicalDurationRange, 12–21 days]
-
A.
typicalDurationDays
chosen
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
B.
typicalRecordingDuration
Indicates the usual or standard length of time that something is recorded.
-
C.
typicalTourDuration
Indicates the usual length of time that a tour normally takes to complete.
-
D.
banDurationApproximate
Indicates that the duration of a ban is known only approximately rather than as an exact, precise time period.
-
E.
typicalTrackLengthRange
Indicates the usual minimum and maximum lengths that a track associated with something tends to fall between.
- 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_69ca82bfeb6481909d07b91b5cf69f59 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb455213f08190a4327a2116c7381f |
completed | March 31, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69cb36a0847c8190af9038aef78319b3 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:38 p.m.