Triple
T20935083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abell 3627 |
E515562
|
entity |
| Predicate | liesInZoneOfAvoidance |
P9997
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Abell 3627, liesInZoneOfAvoidance, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liesInZoneOfAvoidance Context triple: [Abell 3627, liesInZoneOfAvoidance, yes]
-
A.
locatedOutsideGalaxy
Indicates that one entity exists in a position that is external to, and not contained within, the boundaries of a specified galaxy.
-
B.
isInGalaxy
Indicates that one astronomical object is located within or belongs to a particular galaxy.
-
C.
inHabitableZoneOf
Indicates that one celestial body orbits within the region around another where conditions are suitable for liquid water and potentially habitable environments.
-
D.
isNearbyGalaxyOf
Indicates that one galaxy is located relatively close in space to another galaxy, within a limited cosmic distance.
-
E.
locatedInSkyRegion
chosen
Indicates that an entity is situated within or associated with a specific region or area of the sky.
- 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_69e0b4fc13408190b06868df03c5c29b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f950d5e081908ec0df4824cf69f7 |
completed | April 21, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:49 p.m.