Triple
T22279514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abell 426 |
E550692
|
entity |
| Predicate | hasAbellNumber |
P147671
|
FINISHED |
| Object | 426 |
—
|
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: 426 | Statement: [Abell 426, hasAbellNumber, 426]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAbellNumber Context triple: [Abell 426, hasAbellNumber, 426]
-
A.
hasCaldwellNumber
Indicates that an astronomical object is associated with a specific entry in the Caldwell catalog, identified by its Caldwell number.
-
B.
hasHellyNumber
Indicates that there exists a smallest integer h such that, for this family of sets, any subfamily in which every h sets have a nonempty intersection must itself have a nonempty overall intersection.
-
C.
hasMessierNumber
Indicates that an astronomical object is identified by a specific catalog entry in the Messier catalog.
-
D.
caldwellNumber
Indicates that there is a numerical value associated with an entity that represents its Caldwell number, typically quantifying a specific property or characteristic defined by the Caldwell metric.
-
E.
hasNGCNumber
Indicates that an astronomical object is identified by a specific catalog entry in the New General Catalogue (NGC).
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f14eaa8cec819081c2ad031154ebe7 |
completed | April 29, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:40 p.m.