Triple
T4564653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pura Segara Anak |
E121879
|
entity |
| Predicate | altitudeContext |
P21978
|
FINISHED |
| Object | high-altitude mountain temple |
—
|
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-altitude mountain temple | Statement: [Pura Segara Anak, altitudeContext, high-altitude mountain temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: altitudeContext Context triple: [Pura Segara Anak, altitudeContext, high-altitude mountain temple]
-
A.
elevationContext
chosen
Indicates the contextual relationship between an entity and its elevation or vertical position relative to a reference point or environment.
-
B.
altitudeEffect
Indicates how a change in altitude influences or modifies some property, condition, or outcome.
-
C.
altitudeCategory
Indicates the classification of something based on its height or elevation relative to a reference level (e.g., low, medium, high altitude).
-
D.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
E.
altitudeProfile
Indicates the variation of elevation or height along a path, route, or trajectory over distance or time.
- 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd589b439c81908da9d19433310bcd |
completed | March 20, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.