Triple
T18458173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 90377 Sedna |
E450958
|
entity |
| Predicate | distanceFromSunAtDiscovery |
P59281
|
FINISHED |
| Object | about 90 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: about 90 AU | Statement: [90377 Sedna, distanceFromSunAtDiscovery, about 90 AU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromSunAtDiscovery Context triple: [90377 Sedna, distanceFromSunAtDiscovery, about 90 AU]
-
A.
approximateDistanceFromSun
chosen
Indicates an estimated or rough measure of how far an entity is from the Sun, rather than an exact distance.
-
B.
distanceFromSunCategory
Indicates the qualitative category or range into which an entity’s distance from the Sun falls (e.g., very close, moderate, far).
-
C.
distanceFromEarth
Indicates the measured or calculated spatial separation between an entity and the planet Earth.
-
D.
hasMeanDistanceFromSun
Indicates that an entity (typically a celestial body) is characterized by a specific average distance from the Sun.
-
E.
SunDistanceFromCenter
Indicates the distance between the Sun and the central reference point of a specified system (such as a galaxy or coordinate frame).
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a7c18d88190ac17f58111722223 |
completed | April 19, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:31 a.m.