Triple
T20576686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M75 |
E505235
|
entity |
| Predicate | hasHalfLightRadius |
P40628
|
FINISHED |
| Object | ~0.9 arcminutes |
—
|
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: ~0.9 arcminutes | Statement: [M75, hasHalfLightRadius, ~0.9 arcminutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHalfLightRadius Context triple: [M75, hasHalfLightRadius, ~0.9 arcminutes]
-
A.
halfLightRadius
chosen
Indicates the radius within which half of an object's total emitted light is contained.
-
B.
hasRadiusRange
Indicates that there is a specified minimum and maximum radius within which the related entity or feature falls.
-
C.
hasRadiusType
Indicates that an entity has a radius characterized by a specific type or classification.
-
D.
isInHalf
Indicates that one entity is located within or belongs to a specified half or subdivision of another entity.
-
E.
hasMeanRadius
Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
- 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_69e0b4b721588190993ac7b0a9be2736 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a90af3608190955d2c7950726178 |
completed | April 20, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:39 a.m.