Triple
T28513372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baringo–Bogoria basin |
E721550
|
entity |
| Predicate | isTectonically |
P17577
|
FINISHED |
| Object | active |
—
|
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: active | Statement: [Baringo–Bogoria basin, isTectonically, active]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTectonically Context triple: [Baringo–Bogoria basin, isTectonically, active]
-
A.
isTectonicFeature
Indicates that something is a geological structure or formation resulting from tectonic processes or plate movements.
-
B.
isPartOfTectonicFeature
Indicates that one geological entity is a component or subdivision of a larger tectonic feature or structure.
-
C.
hasTectonicSetting
chosen
Indicates the geological or tectonic environment in which an entity (such as a rock unit, region, or event) is situated or formed.
-
D.
isFedByTectonicPlate
Indicates that something (such as a geological feature or process) receives material, energy, or influence from the movement or interaction of a specific tectonic plate.
-
E.
hasTypeOfTectonicFeature
Indicates that one entity is characterized by or classified as a specific type of tectonic feature (such as a fault, plate boundary, or rift).
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64f7704748190b4d9bdebe3b827bc |
completed | May 2, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:14 a.m.