Triple

T9431006
Position Surface form Disambiguated ID Type / Status
Subject Aquamarine E227373 entity
Predicate typicalGeologicEnvironment P88863 FINISHED
Object granite pegmatites — 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: granite pegmatites | Statement: [Aquamarine, typicalGeologicEnvironment, granite pegmatites]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalGeologicEnvironment
Context triple: [Aquamarine, typicalGeologicEnvironment, granite pegmatites]
  • A. geologicalSystem
    Indicates that one entity is a geological system (e.g., rock units, structures, or processes forming a coherent geologic framework) associated with or characterizing the other entity.
  • B. geologicType
    Indicates the specific geological classification or category assigned to a rock, soil, or earth material unit.
  • C. depositionalEnvironment
    Indicates the natural setting or conditions under which sediments were originally deposited.
  • D. geologicalFormation
    Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
  • E. regionalGeologyContext
    Indicates the broader geological setting or framework within which a specific geological feature, event, or observation occurs.
  • 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_69ca8437a7ac81908651de48f2d2141d completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd7e5ed7408190beda5fb078e9345a completed April 1, 2026, 8:21 p.m.
PD Predicate disambiguation batch_69cca55548488190b171ae695a3212de completed April 1, 2026, 4:55 a.m.
PDg Predicate description generation batch_69cca89b3368819087a3d69270c1f185 completed April 1, 2026, 5:09 a.m.
Created at: March 30, 2026, 7:49 p.m.