Triple
T24841084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinyero Special Nature Reserve |
E621613
|
entity |
| Predicate | mainGeologicalOrigin |
P89872
|
FINISHED |
| Object | volcanic |
—
|
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: volcanic | Statement: [Chinyero Special Nature Reserve, mainGeologicalOrigin, volcanic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainGeologicalOrigin Context triple: [Chinyero Special Nature Reserve, mainGeologicalOrigin, volcanic]
-
A.
hasGeologicalNature
chosen
Indicates that something possesses a specific geological character, composition, or formation type.
-
B.
geologicalOriginRegion
Indicates the geographic region from which a geological feature, material, or formation originally derives.
-
C.
geologicalOriginOfStones
Indicates the geological source or formation process from which particular stones originate.
-
D.
geologicalRole
Indicates the functional or classificatory role an entity plays within geological processes, structures, or contexts.
-
E.
geologyRelatedTo
Indicates a relationship where one geological entity, feature, or concept is connected, associated, or relevant to another within the domain of geology.
- 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:18 a.m.