Triple
T12176100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 7319 |
E290090
|
entity |
| Predicate | hasRedshift |
P22404
|
FINISHED |
| Object | 0.02251 |
—
|
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.02251 | Statement: [NGC 7319, hasRedshift, 0.02251]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRedshift Context triple: [NGC 7319, hasRedshift, 0.02251]
-
A.
redshift
Indicates that the observed wavelength of light or other electromagnetic radiation from an object is shifted toward longer (redder) wavelengths, typically due to relative motion away from the observer or cosmic expansion.
-
B.
occursAtRedshift
Indicates that an event or phenomenon takes place at a specified cosmological redshift value.
-
C.
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.
-
D.
hasPrestoMachines
Indicates that an entity possesses or is equipped with one or more Presto machines.
-
E.
hasRapids
Indicates that a body of water contains sections of fast-flowing, turbulent water known as rapids.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91621ca6c81908365732f361aef13 |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150e85348190b9b47cda4a17dcd0 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.