Triple
T15086552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalampaka |
E360287
|
entity |
| Predicate | terrainFeatureNearby |
P2064
|
FINISHED |
| Object | sandstone rock pillars |
—
|
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: sandstone rock pillars | Statement: [Kalampaka, terrainFeatureNearby, sandstone rock pillars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terrainFeatureNearby Context triple: [Kalampaka, terrainFeatureNearby, sandstone rock pillars]
-
A.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
-
B.
nearbyElevation
Indicates that one entity is located at or associated with an elevation that is geographically close to the elevation of another entity.
-
C.
nearbyFeature
chosen
Indicates that one entity is located close to or in the immediate vicinity of another entity.
-
D.
hasNearbyLandscapeType
Indicates that one entity is located close to, or in the vicinity of, a particular type of landscape.
-
E.
nearbyMountainRegion
Indicates that one location is situated close to or within the surrounding area of a mountainous region.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00276d1608190bc310d5b86ecd1d5 |
completed | April 15, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:03 a.m.