Triple
T19122454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Amnye Machen |
E468081
|
entity |
| Predicate | pilgrimageCircuitLength |
P44364
|
FINISHED |
| Object | about 120–150 km |
—
|
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 120–150 km | Statement: [Mount Amnye Machen, pilgrimageCircuitLength, about 120–150 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pilgrimageCircuitLength Context triple: [Mount Amnye Machen, pilgrimageCircuitLength, about 120–150 km]
-
A.
containsPilgrimageCircuit
Indicates that a location or area includes within it a defined route or set of sites followed as part of a pilgrimage.
-
B.
pilgrimageRouteTo
Indicates a route or path that is traditionally used or designated for making a religious or spiritual pilgrimage to a particular destination.
-
C.
pilgrimageNumber
Indicates the number or count associated with a particular pilgrimage event or journey.
-
D.
circuitLength
chosen
Indicates the total measured length or distance of a circuit or closed path.
-
E.
pilgrimageScale
Indicates the extent or magnitude of a pilgrimage-related activity, such as its size, intensity, or level of significance.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3c9dfcc819090f8424608892cb3 |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.