Triple
T16825642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOAR Telescope |
E409010
|
entity |
| Predicate | hasLocationAltitude |
P21269
|
FINISHED |
| Object | high-altitude site in the Andes |
—
|
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 site in the Andes | Statement: [SOAR Telescope, hasLocationAltitude, high-altitude site in the Andes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocationAltitude Context triple: [SOAR Telescope, hasLocationAltitude, high-altitude site in the Andes]
-
A.
locatedAtAltitude
chosen
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
B.
hasAltitudeStation
Indicates that something is associated with or located at a station characterized by a specific altitude.
-
C.
hasAltitudeFeature
Indicates that an entity possesses a characteristic or attribute related to its elevation or vertical position above a reference level.
-
D.
hasApproxElevationFeet
Indicates that an entity is associated with an elevation value measured in feet that is approximate rather than exact.
-
E.
extendsFromAltitude
Indicates a relationship where something stretches or reaches outward starting from a specified altitude.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b3126db88190ac5595b0d50e4232 |
completed | April 18, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.