Triple
T28483106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mani Rimdu festival |
E720746
|
entity |
| Predicate | performedAtAltitude |
P185305
|
FINISHED |
| Object | high Himalayan altitude |
—
|
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: high Himalayan altitude | Statement: [Mani Rimdu festival, performedAtAltitude, high Himalayan altitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedAtAltitude Context triple: [Mani Rimdu festival, performedAtAltitude, high Himalayan altitude]
-
A.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
B.
operationalAltitude
Indicates the typical or designated altitude at which an entity is intended to operate.
-
C.
meetsAtAltitude
Indicates that two or more entities come together or intersect at a specific vertical height or elevation.
-
D.
extendsFromAltitude
Indicates a relationship where something stretches or reaches outward starting from a specified altitude.
-
E.
altitudeAchieved
Indicates that an entity has reached or attained a specified altitude.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be520f148190ba200bf3dbf40656 |
completed | May 3, 2026, 9:29 p.m. |
Created at: April 28, 2026, 2:56 a.m.