Triple
T5940517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shapley Supercluster |
E132154
|
entity |
| Predicate | hasApproximateRedshift |
P22404
|
FINISHED |
| Object | z ≈ 0.046 |
—
|
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: z ≈ 0.046 | Statement: [Shapley Supercluster, hasApproximateRedshift, z ≈ 0.046]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateRedshift Context triple: [Shapley Supercluster, hasApproximateRedshift, z ≈ 0.046]
-
A.
redshift_z
chosen
Indicates the cosmological redshift value associated with an object or event, representing how much its emitted light has been stretched by the expansion of the universe.
-
B.
hasApproximateDistanceScale
Indicates that one entity is related to another by a distance measure that is approximate or estimated rather than exact.
-
C.
hasApproximateCoordinates
Indicates that an entity is associated with location coordinates that are estimated or imprecise rather than exact.
-
D.
hasApproximateValue
Indicates that one entity’s value is close to, but not exactly equal to, the value of another entity within an acceptable margin of error.
-
E.
hasApproximateDepth
Indicates that an entity is associated with a depth value that is not exact but estimated or approximate.
- 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_69c0085c55dc8190aa90e242c956e2fa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03f26f51881908cc253fe5775a1fc |
completed | March 22, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69c03355caf08190b960563a1aed23f9 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:01 p.m.