Triple
T4911685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andromeda VI |
E110246
|
entity |
| Predicate | halfLightRadius_approx |
P40628
|
FINISHED |
| Object | 1.0 kiloparsecs |
—
|
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: 1.0 kiloparsecs | Statement: [Andromeda VI, halfLightRadius_approx, 1.0 kiloparsecs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: halfLightRadius_approx Context triple: [Andromeda VI, halfLightRadius_approx, 1.0 kiloparsecs]
-
A.
halfLightRadius
chosen
Indicates the radius within which half of an object's total emitted light is contained.
-
B.
approximateRadius
Indicates that one entity specifies or provides an estimated value for the radius of another entity.
-
C.
lightRange
Indicates the distance or area over which a light source effectively emits or illuminates.
-
D.
hasMeanRadius
Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
-
E.
approximateDiameter
Indicates that one entity specifies the estimated or rough measurement of another entity’s diameter.
- 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_69bd44132b94819088522d92beaadc78 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e9c32148190a940a3733ecd1898 |
completed | March 20, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69bd6c325e188190823836d79934e9bc |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.