Triple
T22430553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S Monocerotis |
E554485
|
entity |
| Predicate | hasBrightnessVariation |
P132952
|
FINISHED |
| Object | changes brightness over time |
—
|
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: changes brightness over time | Statement: [S Monocerotis, hasBrightnessVariation, changes brightness over time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrightnessVariation Context triple: [S Monocerotis, hasBrightnessVariation, changes brightness over time]
-
A.
hasVariableBrightness
Indicates that the brightness of an entity is not constant but changes over time or under different conditions.
-
B.
brightnessVariation
chosen
Indicates a change or fluctuation in the level of brightness of an entity over time or across conditions.
-
C.
hasLightVariationCause
Indicates that one thing is the reason or source for a change or variation in light associated with another thing.
-
D.
isBright
Indicates that an entity emits or reflects a high level of light, making it visually intense or luminous.
-
E.
hasLightness
Indicates that one entity possesses or exhibits a certain degree or quality of lightness (such as brightness or value) in relation to another.
- 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_69e11e4f2d0c819091aa3558ea2ee630 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a311b148190bdb752f3f067bb3f |
completed | April 29, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.