Triple

T18491515
Position Surface form Disambiguated ID Type / Status
Subject Liber Primus E451826 entity
Predicate hasHeliocentricModel P20343 FINISHED
Object Sun at the center of the universe 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: Sun at the center of the universe | Statement: [Liber Primus, hasHeliocentricModel, Sun at the center of the universe]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHeliocentricModel
Context triple: [Liber Primus, hasHeliocentricModel, Sun at the center of the universe]
  • A. hasHeliocentricOrbit
    Indicates that an object follows an orbital path around the Sun as its central body.
  • B. usesPlanetaryModel
    Indicates that one entity employs or is based on a planetary (e.g., orbiting bodies) model in relation to another entity or context.
  • C. hasHeliosphere
    Indicates that an object possesses a surrounding region of space dominated by its own stellar wind and magnetic field, known as a heliosphere.
  • D. celestialHierarchy
    Indicates a ranked or ordered relationship among celestial entities, where some hold higher or more authoritative positions than others.
  • E. hasRelationToSun chosen
    Indicates a relationship in which an entity is connected or related in some way to the Sun.
  • 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_69d8d3855d50819097fc8561b0299dd9 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e531dcac3c8190b2ebd129ca7f368d completed April 19, 2026, 7:49 p.m.
PD Predicate disambiguation batch_69e469d671088190b619de96ea6f92ab completed April 19, 2026, 5:36 a.m.
Created at: April 10, 2026, 11:35 a.m.