Triple
T1528656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epsilon Eridani |
E32390
|
entity |
| Predicate | EpsilonEridani_b_minimumMass_Jupiter |
P29859
|
FINISHED |
| Object | about 0.8 to 1.5 |
—
|
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: about 0.8 to 1.5 | Statement: [Epsilon Eridani, EpsilonEridani_b_minimumMass_Jupiter, about 0.8 to 1.5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EpsilonEridani_b_minimumMass_Jupiter Context triple: [Epsilon Eridani, EpsilonEridani_b_minimumMass_Jupiter, about 0.8 to 1.5]
-
A.
relativeSizeToEarth
Indicates the comparative size of an entity when measured relative to the size of Earth.
-
B.
innerBoundaryDistanceFromSun
Indicates the distance from the Sun to the inner boundary of a specified region or zone.
-
C.
closestApproachDistanceToJupiter
Indicates the minimum distance an object comes to Jupiter during its trajectory or orbit.
-
D.
hasEquatorialDiameter_km
Indicates the measurement, in kilometers, of an object's diameter across its equator.
-
E.
isOneOfMostMassiveTransNeptunianObjects
Indicates that the subject is among the most massive known objects located beyond Neptune in the Solar System.
- 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.