Triple
T19395680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R Doradus |
E485182
|
entity |
| Predicate | variableMagnitudeRange |
P136288
|
FINISHED |
| Object | 4.8–6.6 |
—
|
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: 4.8–6.6 | Statement: [R Doradus, variableMagnitudeRange, 4.8–6.6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: variableMagnitudeRange Context triple: [R Doradus, variableMagnitudeRange, 4.8–6.6]
-
A.
meanGbandMagnitudeRange
Indicates that the relationship concerns the range (difference between maximum and minimum) of mean G-band magnitudes measured for an entity.
-
B.
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.
-
C.
maximumMagnitude
Indicates the greatest absolute value or intensity that a quantity, measurement, or effect can reach within a given context.
-
D.
magnitudeScale
Indicates the scale or measurement system used to quantify the magnitude or intensity of something.
-
E.
rangeVariant
Indicates that one entity is a variant or alternative form within the value range defined or covered by another entity.
- F. None of above. chosen
Provenance (4 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61b4875ac8190a9c184c075b5db16 |
completed | April 20, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69e50213571881909cd7543a43b51986 |
completed | April 19, 2026, 4:25 p.m. |
Created at: April 10, 2026, 1:36 p.m.