Triple
T13180135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2004 DW |
E313699
|
entity |
| Predicate | heliocentricDistanceRange |
P59281
|
FINISHED |
| Object | roughly 30–49 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: roughly 30–49 AU | Statement: [2004 DW, heliocentricDistanceRange, roughly 30–49 AU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heliocentricDistanceRange Context triple: [2004 DW, heliocentricDistanceRange, roughly 30–49 AU]
-
A.
planetOrbitalDistance
Indicates the average distance between a planet and the celestial body it orbits, typically measured along its orbital path.
-
B.
approximateDistanceFromSun
chosen
Indicates an estimated or rough measure of how far an entity is from the Sun, rather than an exact distance.
-
C.
hasMeanDistanceFromSun
Indicates that an entity (typically a celestial body) is characterized by a specific average distance from the Sun.
-
D.
distanceFromSunCategory
Indicates the qualitative category or range into which an entity’s distance from the Sun falls (e.g., very close, moderate, far).
-
E.
distanceFromEarth
Indicates the measured or calculated spatial separation between an entity and the planet Earth.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:14 p.m.