Triple
T9838198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messier 16 |
E239154
|
entity |
| Predicate | hasDustComponent |
P82946
|
FINISHED |
| Object | interstellar dust |
—
|
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: interstellar dust | Statement: [Messier 16, hasDustComponent, interstellar dust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDustComponent Context triple: [Messier 16, hasDustComponent, interstellar dust]
-
A.
hasDust
chosen
Indicates that one entity possesses, contains, or is covered with dust.
-
B.
hasExtendedDustyRegion
Indicates that an entity possesses a surrounding area or zone characterized by dust that extends outward beyond its immediate vicinity.
-
C.
hasDustExtinction
Indicates that an entity exhibits or is subject to attenuation of light due to the presence of intervening dust.
-
D.
hasDustLanes
Indicates that an object exhibits distinct, lane-like regions of dust that obscure or separate its brighter components.
-
E.
hasAirComponent
Indicates that something includes, contains, or is associated with an air-related component or element.
- 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb347ff4c81908c312548a25bae71 |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:33 p.m.