Triple
T30038414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tao-Rusyr |
E763226
|
entity |
| Predicate | calderaContains |
P50363
|
FINISHED |
| Object | Kol’tsevoe Lake |
—
|
NE NERFINISHED |
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: Kol’tsevoe Lake | Statement: [Tao-Rusyr, calderaContains, Kol’tsevoe Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calderaContains Context triple: [Tao-Rusyr, calderaContains, Kol’tsevoe Lake]
-
A.
calderaName
Indicates that an entity is assigned the proper name of a caldera.
-
B.
calderaStructure
Indicates a structural or morphological relationship in which one geological feature forms, defines, or contributes to the caldera configuration of another.
-
C.
locatedInCalderaOf
chosen
Indicates that one entity is situated within the caldera (the large volcanic crater) of another entity.
-
D.
calderaSystem
Indicates a geological relationship where a volcanic system is associated with, contained within, or characterized by a caldera structure.
-
E.
containsCaldera
Indicates that one geological feature, typically a volcano or volcanic region, has a caldera located within its bounds.
- 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_69f2246fb2b88190acff36bf7975c8f0 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f679d678188190a350aabf7e8f9c14 |
completed | May 2, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:52 p.m.