Triple
T18443121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UGC 6456 |
E450582
|
entity |
| Predicate | distanceFromLocalGroup |
P120034
|
FINISHED |
| Object | near the Local Group boundary |
—
|
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: near the Local Group boundary | Statement: [UGC 6456, distanceFromLocalGroup, near the Local Group boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromLocalGroup Context triple: [UGC 6456, distanceFromLocalGroup, near the Local Group boundary]
-
A.
isNearbyGalaxyGroup
Indicates that one galaxy group is located at a relatively close distance to another galaxy group in astronomical terms.
-
B.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
C.
distancesFrom
chosen
Indicates the measured spatial separation between one entity and one or more other entities.
-
D.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
E.
distanceFromCentre
Indicates the measured or specified distance of an entity from a defined central point.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c12a0248190a848a1fe833a1975 |
completed | April 19, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:30 a.m.