Triple

T540551
Position Surface form Disambiguated ID Type / Status
Subject Lomonosov Ridge E12617 entity
Predicate geologicalNature P4015 FINISHED
Object continental crust feature 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 feature | Statement: [Lomonosov Ridge, geologicalNature, continental crust feature]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: geologicalNature
Context triple: [Lomonosov Ridge, geologicalNature, continental crust feature]
  • A. geologicalFormation chosen
    Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
  • B. geologicalRole
    Indicates the functional or classificatory role an entity plays within geological processes, structures, or contexts.
  • C. causesGeologicalProcess
    Indicates that one entity brings about, initiates, or is responsible for a geological process occurring in another or in the environment.
  • D. hasGeologicalSignificance
    Indicates that something possesses notable importance or relevance within a geological context, such as Earth’s structure, history, or processes.
  • E. naturalResources
    Indicates that one entity possesses, contains, or is a source of natural resources for 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_69a49334226c81908b0ea1689ef6aa3f completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4985feee481908184a39210feab95 completed March 1, 2026, 7:49 p.m.
PD Predicate disambiguation batch_69a494b67c308190a1a225ab7c4b74c6 completed March 1, 2026, 7:34 p.m.
Created at: March 1, 2026, 7:32 p.m.