Triple

T4618248
Position Surface form Disambiguated ID Type / Status
Subject Caloris Basin E100918 entity
Predicate hasAntipodalRegion P56984 FINISHED
Object weird terrain of Mercury 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: weird terrain of Mercury | Statement: [Caloris Basin, hasAntipodalRegion, weird terrain of Mercury]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAntipodalRegion
Context triple: [Caloris Basin, hasAntipodalRegion, weird terrain of Mercury]
  • A. hasRegion
    Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
  • B. meetsAtPolesWith
    Indicates that two entities intersect or come into contact specifically at their polar regions or endpoints.
  • C. isRegionOf
    Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
  • D. hasPeakUsageInHemisphere
    Indicates that the time period of highest usage or activity for something occurs within a specified hemisphere (e.g., Northern or Southern).
  • E. hasIslandOnOneSide
    Indicates that one side of an object, area, or boundary is adjacent to or bordered by an island.
  • 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_69bd43cf363c819087fd5ab441b4a3f4 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd59e247448190ad92f194cb1127c5 completed March 20, 2026, 2:29 p.m.
PD Predicate disambiguation batch_69bd522fd5c48190ad2bffc0a5bc9061 completed March 20, 2026, 1:57 p.m.
PDg Predicate description generation batch_69bd556b93cc8190ab817d2817109a0b completed March 20, 2026, 2:10 p.m.
Created at: March 20, 2026, 1:12 p.m.