Triple

T16200394
Position Surface form Disambiguated ID Type / Status
Subject Amor group E393182 entity
Predicate perihelionDistanceCriterion P20360 FINISHED
Object q > 1.017 AU 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: q > 1.017 AU | Statement: [Amor group, perihelionDistanceCriterion, q > 1.017 AU]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: perihelionDistanceCriterion
Context triple: [Amor group, perihelionDistanceCriterion, q > 1.017 AU]
  • A. perihelionDistance chosen
    Indicates the shortest distance between an orbiting body and the Sun along its orbital path.
  • B. perihelionInsideOrbitOf
    Indicates that the perihelion (closest point to the Sun) of one object's orbit lies within the orbital path of another object.
  • C. perihelionOutsideOrbitOf
    Indicates that the closest point of one object's orbit to the Sun (its perihelion) lies outside the orbital path of another object.
  • D. hasAphelionNear
    Indicates that one celestial body's aphelion (its farthest point from the object it orbits) lies close to another specified reference point or object.
  • E. hasPerihelionInside
    Indicates that an object's closest point to the Sun (its perihelion) lies within the boundary or interior of another specified region or orbit.
  • 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_69d87f1f5bd08190bd01cac0d5b9d2ef completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e22709b0d88190b40787e0520d02ab completed April 17, 2026, 12:26 p.m.
PD Predicate disambiguation batch_69e219e11f6081909106b1240a17fd37 completed April 17, 2026, 11:30 a.m.
Created at: April 10, 2026, 5:03 a.m.