Triple
T33644662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banda region |
E861925
|
entity |
| Predicate | hasTectonicComplexity |
P66363
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Banda region, hasTectonicComplexity, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTectonicComplexity Context triple: [Banda region, hasTectonicComplexity, high]
-
A.
hasTectonicSetting
Indicates the geological or tectonic environment in which an entity (such as a rock unit, region, or event) is situated or formed.
-
B.
hasTectonicStability
Indicates that an entity (such as a region or planetary surface) experiences relatively low tectonic activity and maintains structural stability over time.
-
C.
hasComplexGeology
chosen
Indicates that an entity possesses geologic features or structure that are intricate, varied, or highly heterogeneous rather than simple or uniform.
-
D.
hasTectonicAffinity
Indicates a relationship where one geological unit or feature shares a common tectonic origin, setting, or structural association with another.
-
E.
isTectonicFeature
Indicates that something is a geological structure or formation resulting from tectonic processes or plate movements.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 1, 2026, 1:42 a.m.