Triple
T3569169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batagay |
E75525
|
entity |
| Predicate | nearGeologicalFeature |
P2064
|
FINISHED |
| Object | thermokarst depression |
—
|
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: thermokarst depression | Statement: [Batagay, nearGeologicalFeature, thermokarst depression]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearGeologicalFeature Context triple: [Batagay, nearGeologicalFeature, thermokarst depression]
-
A.
nearbyFeature
chosen
Indicates that one entity is located close to or in the immediate vicinity of another entity.
-
B.
nearestLandmass
Indicates that one landmass is the closest geographically to another specified point or landmass.
-
C.
geologicalFormation
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
-
D.
nearVolcano
Indicates that one entity is located in close proximity to a volcano.
-
E.
followsNaturalFeature
Indicates that one entity’s position, path, or boundary runs alongside or is aligned with a natural geographic feature (such as a river, coastline, or ridgeline).
- 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_69ad85d512708190829c8b2d3a2ccfb8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0c083ac8190a71cd9ede2114cac |
completed | March 8, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69adb8364d848190a96a9bc7a6126af2 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.