Triple
T23438442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunda Craton |
E565330
|
entity |
| Predicate | hasLithosphereType |
P15600
|
FINISHED |
| Object | continental lithosphere |
—
|
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: continental lithosphere | Statement: [Sunda Craton, hasLithosphereType, continental lithosphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLithosphereType Context triple: [Sunda Craton, hasLithosphereType, continental lithosphere]
-
A.
lithosphereType
chosen
Indicates the classification of a lithospheric unit according to its type (e.g., oceanic, continental, or other defined categories).
-
B.
hasTectonicAffinity
Indicates a relationship where one geological unit or feature shares a common tectonic origin, setting, or structural association with another.
-
C.
hasCrustalType
Indicates that an object or location is associated with a specific type or classification of crust (e.g., continental, oceanic).
-
D.
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).
-
E.
lithosphericThickness
Indicates the measured or modeled thickness of a planet’s lithosphere at a given location or region.
- 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_69e24584f9488190bb32730bd2ce023e |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5dda7448190b6c686e0db4f4f2f |
completed | April 29, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:50 p.m.