Triple

T33965057
Position Surface form Disambiguated ID Type / Status
Subject Montes Caucasus E870826 entity
Predicate extendsFromFeature P177972 FINISHED
Object vicinity of crater Eudoxus 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: vicinity of crater Eudoxus | Statement: [Montes Caucasus, extendsFromFeature, vicinity of crater Eudoxus]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: extendsFromFeature
Context triple: [Montes Caucasus, extendsFromFeature, vicinity of crater Eudoxus]
  • A. extendsTo
    Indicates that one entity reaches, stretches, or continues its scope, influence, or coverage up to or into another entity.
  • B. extendedFrom
    Indicates that one entity is derived by adding to or building upon the scope, content, or structure of another entity.
  • C. usesExtensionOf
    Indicates that one entity makes use of another entity that is an extension or extended version of something else.
  • D. extendedBy
    Indicates that one entity builds upon, enlarges, or adds to the scope, functionality, or duration of another entity.
  • E. inheritedFrom
    Indicates that one entity has received or derived something (such as traits, rights, or property) from another entity, typically a predecessor or ancestor.
  • 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_69f3499ce8e88190b66e1d49ad8c7037 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f7064e906881909c3186c646145d34 completed May 3, 2026, 8:24 a.m.
PD Predicate disambiguation batch_69f70100ec1c8190a6b97f50e88891f2 completed May 3, 2026, 8:02 a.m.
PDg Predicate description generation batch_69f7064d37388190993b2a7305a02b9f completed May 3, 2026, 8:24 a.m.
Created at: May 1, 2026, 1:50 a.m.