Triple
T21348053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 2362 |
E526393
|
entity |
| Predicate | hasLittleNebulosity |
P135119
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NGC 2362, hasLittleNebulosity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLittleNebulosity Context triple: [NGC 2362, hasLittleNebulosity, true]
-
A.
hasNebulosity
chosen
Indicates that one entity possesses or exhibits nebulous, cloud-like, or diffuse characteristics associated with nebulosity.
-
B.
hasVeryLowSurfaceBrightness
Indicates that an entity exhibits an extremely faint or low level of brightness across its visible surface.
-
C.
isNonIonizedNebula
Indicates that the nebula is in a state where its gas is predominantly neutral rather than ionized.
-
D.
hasLowLuminosity
Indicates that an entity emits relatively little light or energy compared to a typical or reference level.
-
E.
associatedNebula
Indicates a relationship where an object or entity is linked or connected to a particular nebula in some relevant way.
- 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_69e0b51cd5cc81909ac1187971e8a8ad |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8ad2d01b481909d9b4813ff37905c |
completed | April 22, 2026, 11:12 a.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:01 p.m.