Triple
T34185583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 7314 |
E876948
|
entity |
| Predicate | showsOpticalVariability |
P131723
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [NGC 7314, showsOpticalVariability, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showsOpticalVariability Context triple: [NGC 7314, showsOpticalVariability, yes]
-
A.
hasLightcurveVariations
chosen
Indicates that an object exhibits measurable changes in its brightness over time, as captured in its lightcurve.
-
B.
hasSpectralVariability
Indicates that an entity exhibits changes or fluctuations in its spectral properties over time or under different conditions.
-
C.
isVariableStar
Indicates that an astronomical object exhibits intrinsic brightness variations over time, classifying it as a variable star.
-
D.
opticalProperty
Indicates a relationship where an entity has or is characterized by a specific optical property, such as how it interacts with or responds to light.
-
E.
hasVariability
Indicates that an entity exhibits variation or fluctuation in its state, value, or characteristics over time or across instances.
- 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_69f349ae640c8190b9cd220b5368d8b6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:55 a.m.