Triple
T18772757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U Sagittarii |
E459055
|
entity |
| Predicate | hasPeriodicBrightnessVariations |
P131723
|
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: [U Sagittarii, hasPeriodicBrightnessVariations, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeriodicBrightnessVariations Context triple: [U Sagittarii, hasPeriodicBrightnessVariations, true]
-
A.
hasBrightSpots
Indicates that an entity possesses one or more areas or points that are noticeably brighter than their surroundings.
-
B.
sensitivityToLight
Indicates a relationship where an entity reacts adversely or more strongly than normal when exposed to light.
-
C.
isBright
Indicates that an entity emits or reflects a high level of light, making it visually intense or luminous.
-
D.
surfaceBrightnessProfile
Indicates the distribution of brightness as a function of position across a surface, typically describing how intensity changes from one region to another.
-
E.
hasLightcurveVariations
chosen
Indicates that an object exhibits measurable changes in its brightness over time, as captured in its lightcurve.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e59336a6b08190819595a55177264e |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.