Triple
T1014579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laniakea Supercluster |
E21901
|
entity |
| Predicate | approximateRadius |
P23277
|
FINISHED |
| Object | 260 million light-years |
—
|
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: 260 million light-years | Statement: [Laniakea Supercluster, approximateRadius, 260 million light-years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateRadius Context triple: [Laniakea Supercluster, approximateRadius, 260 million light-years]
-
A.
approximateDiameter
Indicates that one entity specifies the estimated or rough measurement of another entity’s diameter.
-
B.
hasMeanRadius
Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
-
C.
approximateSize
Indicates that one entity has a size that is roughly or approximately equal to the size of another entity.
-
D.
approximateMass
Indicates that one entity has a mass value that is an estimate or close approximation of the mass of another entity.
-
E.
ringRadius
Indicates the size of a ring by specifying the distance from its center to its outer edge.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7be907c8190b5c6ea89257755a7 |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b72207c08190a3dbb2aa7acbbc71 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7bd3d50819091e6f1d2ffe4c7ee |
completed | March 1, 2026, 10:03 p.m. |
Created at: March 1, 2026, 7:41 p.m.