Triple
T1528663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epsilon Eridani |
E32390
|
entity |
| Predicate | rankByDistanceFromSun |
P29862
|
FINISHED |
| Object | among nearest Sun-like stars |
—
|
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: among nearest Sun-like stars | Statement: [Epsilon Eridani, rankByDistanceFromSun, among nearest Sun-like stars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankByDistanceFromSun Context triple: [Epsilon Eridani, rankByDistanceFromSun, among nearest Sun-like stars]
-
A.
hasMeanDistanceFromSun
Indicates that an entity (typically a celestial body) is characterized by a specific average distance from the Sun.
-
B.
SunDistanceFromCenter
Indicates the distance between the Sun and the central reference point of a specified system (such as a galaxy or coordinate frame).
-
C.
distanceFromEarth
Indicates the measured or calculated spatial separation between an entity and the planet Earth.
-
D.
relativeSizeToEarth
Indicates the comparative size of an entity when measured relative to the size of Earth.
-
E.
innerBoundaryDistanceFromSun
Indicates the distance from the Sun to the inner boundary of a specified region or zone.
- 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_69a885e9b0ac819093a9806ad0efc82c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a933ddc5a881909cdf503f2bc29bd4 |
completed | March 5, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69a907ae8f688190ad9000ea1e018585 |
completed | March 5, 2026, 4:33 a.m. |
| PDg | Predicate description generation | batch_69a933dce3488190b20f0e3d37d16371 |
completed | March 5, 2026, 7:42 a.m. |
Created at: March 4, 2026, 7:26 p.m.