Triple

T30068548
Position Surface form Disambiguated ID Type / Status
Subject Lower Saxony Basin E764109 entity
Predicate hasRockSequence P190349 FINISHED
Object thick Mesozoic sedimentary succession 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: thick Mesozoic sedimentary succession | Statement: [Lower Saxony Basin, hasRockSequence, thick Mesozoic sedimentary succession]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRockSequence
Context triple: [Lower Saxony Basin, hasRockSequence, thick Mesozoic sedimentary succession]
  • A. hasRockRecord
    Indicates that an entity possesses or is associated with a documented record related to rock music or rock materials.
  • B. hasRockType
    Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
  • C. hasRockDrivenSound
    Indicates that something (such as a piece of music or audio) features a sound strongly influenced by rock music characteristics.
  • D. hasRockGrade
    Indicates that an entity is associated with a specific difficulty or quality grade used to classify rock climbing routes or rock features.
  • E. hasRockSubgenre
    Indicates a relationship where one musical style is classified as a subgenre within the broader category of rock music.
  • 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_69f2247221388190a13a22c47094a0ef completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fcc4b700748190ae00b21d09c96695 completed May 7, 2026, 4:58 p.m.
PD Predicate disambiguation batch_69fcb0f9d3d881908a049475182fb039 completed May 7, 2026, 3:34 p.m.
PDg Predicate description generation batch_69fcc4b5f22c8190b8b256adbdc2570c completed May 7, 2026, 4:58 p.m.
Created at: April 29, 2026, 7 p.m.