Triple
T24550318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julcán |
E607343
|
entity |
| Predicate | isInHighlands |
P73807
|
FINISHED |
| Object | Andean highlands |
—
|
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: Andean highlands | Statement: [Julcán, isInHighlands, Andean highlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInHighlands Context triple: [Julcán, isInHighlands, Andean highlands]
-
A.
isOnHighPlains
Indicates that something is located on or situated within a region of elevated, relatively flat high plains.
-
B.
isHighElevation
chosen
Indicates that an entity is located at or associated with a relatively high altitude or elevation above a reference level, typically sea level.
-
C.
isHighlandLandmarkFor
Indicates that a landmark is recognized as a notable or defining feature specifically within a highland area or region.
-
D.
isInValleyOrMountainRegion
Indicates that an entity is located within either a valley area or a mountainous region.
-
E.
isOnHill
Indicates that one entity is located on or atop a hill relative to another reference frame or context.
- 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_69e2c4cae1b88190825e88d5ce8aa61e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8ccddec8190819e6366b3d6b6f0 |
completed | April 30, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:27 a.m.