Triple
T32023871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IM Pegasi |
E817765
|
entity |
| Predicate | radiusPrimary |
P148059
|
FINISHED |
| Object | >10 solar radii (approx) |
—
|
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: >10 solar radii (approx) | Statement: [IM Pegasi, radiusPrimary, >10 solar radii (approx)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radiusPrimary Context triple: [IM Pegasi, radiusPrimary, >10 solar radii (approx)]
-
A.
hasRadiusOfPrimary
chosen
Indicates that an entity (typically an orbiting body or system) is associated with a primary object whose radius is specified by the related value or entity.
-
B.
ringRadius
Indicates the size of a ring by specifying the distance from its center to its outer edge.
-
C.
radiusRatio
Indicates the proportional relationship between one radius and another, typically expressing how large one is relative to the other.
-
D.
designedMajorRadius
Indicates that an entity has a specified primary or largest radius value that was intentionally determined during its design.
-
E.
radiusCategory
Indicates the classification of an entity based on the size or range of its radius.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4684000819090d1f2f28af40db9 |
completed | May 3, 2026, 2:35 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:17 a.m.