Triple
T20216618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth's crust |
E495143
|
entity |
| Predicate | oceanicCrustAverageThickness |
P16324
|
FINISHED |
| Object | about 7 kilometers |
—
|
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: about 7 kilometers | Statement: [Earth's crust, oceanicCrustAverageThickness, about 7 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oceanicCrustAverageThickness Context triple: [Earth's crust, oceanicCrustAverageThickness, about 7 kilometers]
-
A.
lithosphericThickness
Indicates the measured or modeled thickness of a planet’s lithosphere at a given location or region.
-
B.
hasCrustalThickness
chosen
Indicates the relationship in which an object or region possesses a specified thickness of its crust.
-
C.
crustalComposition
Indicates the type and proportion of materials that make up a planet or moon’s outer solid layer (its crust).
-
D.
oceanicPlate
Indicates a relationship where a tectonic plate is classified specifically as an oceanic plate, typically composed of dense, basaltic crust beneath ocean basins.
-
E.
crustType
Indicates the specific style or form of crust associated with an item, such as a pizza or baked good.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66eda2f188190adf39d895e8b99f2 |
completed | April 20, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.