Triple
T24122403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 247 |
E597695
|
entity |
| Predicate | nearbyGalaxyTo |
P65767
|
FINISHED |
| Object | NGC 253 |
—
|
NE NERFINISHED |
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: NGC 253 | Statement: [NGC 247, nearbyGalaxyTo, NGC 253]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyGalaxyTo Context triple: [NGC 247, nearbyGalaxyTo, NGC 253]
-
A.
nearestMajorGalaxyTo
Indicates the relationship in which a given galaxy is the closest major galaxy in space to another specified galaxy.
-
B.
isNearbyGalaxyOf
chosen
Indicates that one galaxy is located relatively close in space to another galaxy, within a limited cosmic distance.
-
C.
oneOfClosestLargeGalaxiesTo
Indicates that the subject is among the nearest galaxies of relatively large size to the specified reference object or location.
-
D.
nearestGalaxyCluster
Indicates that one galaxy cluster is the closest in distance to a given reference object or location compared to all other galaxy clusters.
-
E.
isNearestStarburstGalaxyTo
Indicates that one galaxy is the closest starburst galaxy in space relative to another specified object or location.
- 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_69e288c74200819098ab875b592cb39f |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dee5937c819092396751c23553ca |
completed | April 29, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:05 p.m.