Triple
T12316025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eight-Burst Nebula |
E293600
|
entity |
| Predicate | isDistanceFromEarth |
P7285
|
FINISHED |
| Object | ~2000 light-years |
—
|
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: ~2000 light-years | Statement: [Eight-Burst Nebula, isDistanceFromEarth, ~2000 light-years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDistanceFromEarth Context triple: [Eight-Burst Nebula, isDistanceFromEarth, ~2000 light-years]
-
A.
hasApproximateDistanceFromEarth
Indicates that there is an estimated or non-exact distance between an entity and Earth.
-
B.
distanceFromEarth
chosen
Indicates the measured or calculated spatial separation between an entity and the planet Earth.
-
C.
hasMeanDistanceFromSun
Indicates that an entity (typically a celestial body) is characterized by a specific average distance from the Sun.
-
D.
approximateDistanceFromSun
Indicates an estimated or rough measure of how far an entity is from the Sun, rather than an exact distance.
-
E.
distanceFromSunCategory
Indicates the qualitative category or range into which an entity’s distance from the Sun falls (e.g., very close, moderate, far).
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec5be788190b82d2edc6a0f1095 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.