Triple
T8730813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mimosa |
E207248
|
entity |
| Predicate | hasVariabilityAmplitude_mag |
P51229
|
FINISHED |
| Object | about 0.02 |
—
|
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: about 0.02 | Statement: [Mimosa, hasVariabilityAmplitude_mag, about 0.02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVariabilityAmplitude_mag Context triple: [Mimosa, hasVariabilityAmplitude_mag, about 0.02]
-
A.
exampleMagnitude
Indicates a relationship where one entity serves as a representative or typical instance that illustrates the scale, size, or intensity (magnitude) of another entity or quantity.
-
B.
hasLightcurveAmplitude
chosen
Indicates the measured range of brightness variation (amplitude) in an object's lightcurve over time.
-
C.
maximumMagnitude
Indicates the greatest absolute value or intensity that a quantity, measurement, or effect can reach within a given context.
-
D.
lightcurveAmplitude
Indicates the measured range of brightness variation of an object over time in its light curve.
-
E.
limitingMagnitude
Indicates the faintest detectable level or threshold of an effect, signal, or quantity beyond which it can no longer be reliably observed or measured.
- 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_69ca8358e4008190898471a59b96c301 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d26d280819085e15d4917c2b9a5 |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:37 p.m.