Triple

T20184487
Position Surface form Disambiguated ID Type / Status
Subject Alba Mons E492817 entity
Predicate hasComparison P139014 FINISHED
Object much broader and lower than Olympus Mons 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: much broader and lower than Olympus Mons | Statement: [Alba Mons, hasComparison, much broader and lower than Olympus Mons]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasComparison
Context triple: [Alba Mons, hasComparison, much broader and lower than Olympus Mons]
  • A. hasComparisonCriterion
    Indicates that one entity is used as the basis or standard by which another entity is compared or evaluated.
  • B. isComparedTo
    Indicates that one entity is evaluated or measured in relation to another to highlight similarities, differences, or relative qualities.
  • C. isComparisonSort
    Indicates that the sorting algorithm operates by comparing pairs of elements to determine their order.
  • D. comparisonType
    Indicates the specific kind of comparison being made between two or more values or entities (e.g., equality, inequality, ordering, or similarity).
  • E. comparisonResult
    Indicates the outcome of comparing two entities, typically expressing whether one is less than, equal to, or greater than the other.
  • 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_69da6268a034819081cbd9ea5a1c9475 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e668f199688190a42094cce220f6f2 completed April 20, 2026, 5:57 p.m.
PD Predicate disambiguation batch_69e55b11124c8190babacf2a0fe2d057 completed April 19, 2026, 10:45 p.m.
PDg Predicate description generation batch_69e56700b1a08190ace53cf95827d72d completed April 19, 2026, 11:36 p.m.
Created at: April 11, 2026, 11:36 p.m.