Triple

T3886143
Position Surface form Disambiguated ID Type / Status
Subject Baade E92944 entity
Predicate hasSurfaceFeatureType P47694 FINISHED
Object impact structure 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: impact structure | Statement: [Baade, hasSurfaceFeatureType, impact structure]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSurfaceFeatureType
Context triple: [Baade, hasSurfaceFeatureType, impact structure]
  • A. surfaceFeatureOf chosen
    Indicates that one entity is a surface-level characteristic, pattern, or feature belonging to or present on another entity.
  • B. hasTypeOfTectonicFeature
    Indicates that one entity is characterized by or classified as a specific type of tectonic feature (such as a fault, plate boundary, or rift).
  • C. hasStratigraphicFeature
    Indicates a relationship in which a geological unit, site, or context contains, exhibits, or is associated with a particular stratigraphic feature (such as a layer, horizon, or boundary) within its stratigraphic sequence.
  • D. hasLandscapeFeatures
    Indicates that an entity possesses or includes specific landscape-related characteristics or elements.
  • E. hasSurfaceBody
    Indicates that one entity possesses or is characterized by a particular surface or outer body.
  • 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_69aed9697de0819087c2559295ff3d12 completed March 9, 2026, 2:30 p.m.
NER Named-entity recognition batch_69aeec942bfc8190a398fe370715a28b completed March 9, 2026, 3:51 p.m.
PD Predicate disambiguation batch_69aee759609c8190985e96ec6d96dedd completed March 9, 2026, 3:29 p.m.
Created at: March 9, 2026, 3:20 p.m.