Triple
T19261723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UY Scuti |
E481663
|
entity |
| Predicate | hasRadiusRange |
P135329
|
FINISHED |
| Object | ~1050–1700 solar radii |
—
|
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: ~1050–1700 solar radii | Statement: [UY Scuti, hasRadiusRange, ~1050–1700 solar radii]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRadiusRange Context triple: [UY Scuti, hasRadiusRange, ~1050–1700 solar radii]
-
A.
hasRadiusType
Indicates that an entity has a radius characterized by a specific type or classification.
-
B.
hasAreaRange
Indicates that something’s area falls within a specified minimum-to-maximum range.
-
C.
hasCoveringRadius
Indicates the maximum distance from any point in a space to the nearest point in a given set, defining how well that set covers the space.
-
D.
hasMeanRadius
Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
-
E.
hasClusterRadius
Indicates the radius or spatial extent associated with a particular cluster.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8a022c8190b313e9d11d38e482 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4df51ac6c819091ce72b07790ffa6 |
completed | April 19, 2026, 1:57 p.m. |
Created at: April 10, 2026, 1:28 p.m.