Triple
T19974569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 6868 |
E493656
|
entity |
| Predicate | hasStellarProfile |
P9523
|
FINISHED |
| Object | bright |
—
|
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: bright | Statement: [NGC 6868, hasStellarProfile, bright]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStellarProfile Context triple: [NGC 6868, hasStellarProfile, bright]
-
A.
hasStellarActivity
Indicates that an astronomical object exhibits measurable activity or variability originating from its star, such as flares, spots, or magnetic phenomena.
-
B.
hasProfile
chosen
Indicates that an entity is associated with or possesses a specific profile representation or account.
-
C.
hasStellarEnvironment
Indicates that an object exists within, or is associated with, a particular stellar environment or surrounding stellar conditions.
-
D.
hasStellarStream
Indicates that one astronomical object possesses or is associated with a coherent flow of stars, known as a stellar stream, typically resulting from tidal interactions or disruption.
-
E.
hasStellarShells
Indicates that an astronomical object possesses one or more surrounding shell-like stellar structures.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65bcca5088190b523584d11799400 |
completed | April 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:24 p.m.