Triple

T7658260
Position Surface form Disambiguated ID Type / Status
Subject Epsilon Eridani b E173438 entity
Predicate inclinationConstraint P78598 FINISHED
Object poorly known 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: poorly known | Statement: [Epsilon Eridani b, inclinationConstraint, poorly known]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inclinationConstraint
Context triple: [Epsilon Eridani b, inclinationConstraint, poorly known]
  • A. designedToConstrain
    Indicates that one entity is intentionally created or configured to limit, restrict, or control the behavior, range, or properties of another entity.
  • B. hasIncline
    Indicates that one entity possesses or exhibits a slope, tilt, or upward/downward angle relative to another reference.
  • C. inclinationToEcliptic
    Indicates the angle between an object's orbital plane and the plane of the ecliptic, describing how tilted its orbit is relative to Earth's orbital plane.
  • D. inclinationToEarthEquator
    Indicates the angle between an object's orbital or rotational plane and Earth's equatorial plane.
  • E. constrainedBy
    Indicates that one entity’s state, behavior, or possibilities are limited, restricted, or governed by another entity.
  • 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_69c69955517c819085bc715b96d304d2 completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c7061cbc3c8190a917dd7e71214182 completed March 27, 2026, 10:35 p.m.
PD Predicate disambiguation batch_69c7015dd8fc8190bc5f52a12bd46209 completed March 27, 2026, 10:14 p.m.
PDg Predicate description generation batch_69c7061b218c81909fff789ba4c10e58 completed March 27, 2026, 10:35 p.m.
Created at: March 27, 2026, 3:59 p.m.