Triple
T18854287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UGC 5666 |
E461128
|
entity |
| Predicate | hasSurfaceBrightnessProfile |
P56997
|
FINISHED |
| Object | irregular |
—
|
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: irregular | Statement: [UGC 5666, hasSurfaceBrightnessProfile, irregular]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurfaceBrightnessProfile Context triple: [UGC 5666, hasSurfaceBrightnessProfile, irregular]
-
A.
surfaceBrightnessProfile
chosen
Indicates the distribution of brightness as a function of position across a surface, typically describing how intensity changes from one region to another.
-
B.
surfaceBrightnessClass
Indicates the qualitative classification of how bright an extended object (such as a galaxy) appears per unit area on the sky.
-
C.
sustainedFullScreenBrightness
Indicates that an entity maintains maximum screen brightness continuously for a period of time.
-
D.
supportsWideColorGamut
Indicates that one entity provides or enables compatibility with a wide color gamut capability for another entity or context.
-
E.
maximumBrightness
Indicates the highest level of brightness that an entity can reach or exhibit.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c05b4d8881909af0238f451b0e31 |
completed | April 20, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.