Triple
T22698127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M66 Group |
E561240
|
entity |
| Predicate | redshiftApprox |
P22645
|
FINISHED |
| Object | 0.002 |
—
|
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.002 | Statement: [M66 Group, redshiftApprox, 0.002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redshiftApprox Context triple: [M66 Group, redshiftApprox, 0.002]
-
A.
redshift
chosen
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.
junctionCountApprox
Indicates an approximate count of junctions or connection points involved in or associated with the given entities.
-
C.
approximateEstimation
Indicates an estimation relationship where one value or assessment is only roughly or closely, but not exactly, equal to another.
-
D.
hasApproximateMemberCount
Indicates that an entity is associated with a group or collection for which only an estimated or non-exact number of members is known.
-
E.
lapCountApproximate
Indicates that the recorded number of laps is an estimate rather than an exact, precise count.
- 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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178a008448190b393335704128fe8 |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:14 p.m.