Triple
T16551977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zealandia |
E402093
|
entity |
| Predicate | continentCrustType |
P15600
|
FINISHED |
| Object | continental crust |
—
|
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 crust | Statement: [Zealandia, continentCrustType, continental crust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continentCrustType Context triple: [Zealandia, continentCrustType, continental crust]
-
A.
lithosphereType
chosen
Indicates the classification of a lithospheric unit according to its type (e.g., oceanic, continental, or other defined categories).
-
B.
crustType
Indicates the specific style or form of crust associated with an item, such as a pizza or baked good.
-
C.
crustalComposition
Indicates the type and proportion of materials that make up a planet or moon’s outer solid layer (its crust).
-
D.
continentCollisionType
Indicates the type or nature of the collision occurring between continental landmasses or tectonic plates.
-
E.
continentMargin
Indicates that one entity lies along or forms the boundary region at the edge of a continental landmass relative to another entity.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fc56f9081908bb8f6433a1a688d |
completed | April 18, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:15 a.m.