Triple
T20530354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Group dwarf galaxies |
E504050
|
entity |
| Predicate | typicalHalfLightRadius |
P40628
|
FINISHED |
| Object | tens to thousands of parsecs |
—
|
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: tens to thousands of parsecs | Statement: [Local Group dwarf galaxies, typicalHalfLightRadius, tens to thousands of parsecs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHalfLightRadius Context triple: [Local Group dwarf galaxies, typicalHalfLightRadius, tens to thousands of parsecs]
-
A.
halfLightRadius
chosen
Indicates the radius within which half of an object's total emitted light is contained.
-
B.
lightRange
Indicates the distance or area over which a light source effectively emits or illuminates.
-
C.
innerHaloRadius
Indicates the radius measurement of the inner boundary of a halo-like structure surrounding an object.
-
D.
rayBrightness
Indicates the intensity or luminance level associated with a specific ray.
-
E.
hasRadiusRange
Indicates that there is a specified minimum and maximum radius within which the related entity or feature falls.
- 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_69e0b4b3a6e08190ae663701f50fab8e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a069edf88190835a9c392c990c55 |
completed | April 20, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:37 a.m.