Triple
T18843128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeta Scuti |
E460845
|
entity |
| Predicate | variabilityAmplitude |
P51229
|
FINISHED |
| Object | small amplitude |
—
|
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: small amplitude | Statement: [Zeta Scuti, variabilityAmplitude, small amplitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: variabilityAmplitude Context triple: [Zeta Scuti, variabilityAmplitude, small amplitude]
-
A.
hasVariability
Indicates that an entity exhibits variation or fluctuation in its state, value, or characteristics over time or across instances.
-
B.
amplitudeDefinition
Indicates the relationship by which the amplitude of a signal, wave, or oscillation is formally specified or defined.
-
C.
lightcurveAmplitude
Indicates the measured range of brightness variation of an object over time in its light curve.
-
D.
hasLightcurveAmplitude
chosen
Indicates the measured range of brightness variation (amplitude) in an object's lightcurve over time.
-
E.
flowVariation
Indicates how the rate or pattern of flow (such as water, traffic, or data) changes over time or across different conditions.
- 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_69e5b8eb32548190b2313e877f6ff179 |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.