Triple
T21604873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crux |
E533143
|
entity |
| Predicate | coalsackNebulaType |
P24834
|
FINISHED |
| Object | dark nebula |
—
|
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: dark nebula | Statement: [Crux, coalsackNebulaType, dark nebula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coalsackNebulaType Context triple: [Crux, coalsackNebulaType, dark nebula]
-
A.
isNonIonizedNebula
Indicates that the nebula is in a state where its gas is predominantly neutral rather than ionized.
-
B.
smallMagellanicCloudType
Indicates that something is classified as being of the same type or category as the Small Magellanic Cloud.
-
C.
associatedNebula
chosen
Indicates a relationship where an object or entity is linked or connected to a particular nebula in some relevant way.
-
D.
isTypeOfReflectionNebula
Indicates that one entity is classified as a reflection nebula, i.e., a nebula visible primarily by reflected starlight rather than its own emission.
-
E.
isStarburstGalaxy
Indicates that a galaxy exhibits the intense, short-lived burst of star formation characteristic of a starburst galaxy.
- 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_69e0c46364608190a337dc8720dc2a35 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef17e4a8088190bf51ab2af2369762 |
completed | April 27, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:33 p.m.