Triple
T18485197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UGC 9992 |
E451669
|
entity |
| Predicate | redshiftCategory |
P102097
|
FINISHED |
| Object | nearby galaxy (low redshift) |
—
|
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: nearby galaxy (low redshift) | Statement: [UGC 9992, redshiftCategory, nearby galaxy (low redshift)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redshiftCategory Context triple: [UGC 9992, redshiftCategory, nearby galaxy (low redshift)]
-
A.
classificationRole
chosen
Indicates that one entity serves as a classificatory role or type used to categorize or group another entity.
-
B.
classificationUsedBy
Indicates that a particular classification system or scheme is employed or applied by a given entity.
-
C.
rankingCategory
Indicates the classification or type of ranking under which an entity is evaluated or ordered.
-
D.
classificationAccordingTo
Indicates that an entity is assigned a particular class, type, or category as defined or determined by a specified source, standard, or authority.
-
E.
canonicalCategory
Indicates that an entity is assigned to its primary or standard category within a classification system.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e531d6502c8190af167b954bf8e989 |
completed | April 19, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:35 a.m.