Triple

T7364306
Position Surface form Disambiguated ID Type / Status
Subject Atlantic passive margin E169827 entity
Predicate sedimentaryCoverThickness P77073 FINISHED
Object up to several 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: up to several kilometers | Statement: [Atlantic passive margin, sedimentaryCoverThickness, up to several kilometers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sedimentaryCoverThickness
Context triple: [Atlantic passive margin, sedimentaryCoverThickness, up to several kilometers]
  • A. hasCrustalThickness
    Indicates the relationship in which an object or region possesses a specified thickness of its crust.
  • B. sedimentaryStructure
    Indicates a relationship where a geological entity exhibits or is characterized by a particular sedimentary structure formed during deposition or shortly thereafter.
  • C. lithosphericThickness
    Indicates the measured or modeled thickness of a planet’s lithosphere at a given location or region.
  • D. surfaceRegolithDepth_m
    Indicates the measured thickness of the loose surface regolith layer at a location, expressed in meters.
  • E. hasSedimentaryBasin
    Indicates that a geological region or area contains or is associated with a sedimentary basin.
  • F. None of above. chosen

Provenance (4 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_69c68a5ade988190885b7175f63b7534 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f26d6d6081909c7272a9ccae0d97 completed March 27, 2026, 9:11 p.m.
PD Predicate disambiguation batch_69c6f02d36108190bcb34a95e6a30bd7 completed March 27, 2026, 9:01 p.m.
PDg Predicate description generation batch_69c6f26c050c8190a2d009b45d920490 completed March 27, 2026, 9:11 p.m.
Created at: March 27, 2026, 3:06 p.m.