Triple
T8136850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukrainian Shield |
E189992
|
entity |
| Predicate | maximumCrustalThickness_km |
P16324
|
FINISHED |
| Object | about 45–50 |
—
|
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 45–50 | Statement: [Ukrainian Shield, maximumCrustalThickness_km, about 45–50]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumCrustalThickness_km Context triple: [Ukrainian Shield, maximumCrustalThickness_km, about 45–50]
-
A.
lithosphericThickness
Indicates the measured or modeled thickness of a planet’s lithosphere at a given location or region.
-
B.
maximumDepthKilometres
Indicates the greatest depth, measured in kilometers, that something reaches or extends to.
-
C.
hasCrustalThickness
chosen
Indicates the relationship in which an object or region possesses a specified thickness of its crust.
-
D.
maximumCrustalExtension
Indicates the greatest amount of stretching or thinning that the Earth’s crust has undergone in a given region or event.
-
E.
maximumHeightAboveSeafloor
Indicates the greatest vertical distance between an object or feature and the seafloor beneath it.
- 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_69ca82bd9900819099477cdc2eb4244f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb440171d48190afa4a312ab19389c |
completed | March 31, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69cb369c0d0481908762c488d7f77e74 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:35 p.m.