Triple
T20530505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GCl 104 |
E504053
|
entity |
| Predicate | skyLocationRegion |
P9997
|
FINISHED |
| Object | toward the center of the Milky Way |
—
|
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: toward the center of the Milky Way | Statement: [GCl 104, skyLocationRegion, toward the center of the Milky Way]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skyLocationRegion Context triple: [GCl 104, skyLocationRegion, toward the center of the Milky Way]
-
A.
locatedInSkyRegion
chosen
Indicates that an entity is situated within or associated with a specific region or area of the sky.
-
B.
planetRegion
Indicates that a specified region or area is located on or associated with a particular planet.
-
C.
solarSystemRegion
Indicates that one entity is a region or area located within the solar system that is associated with or contains the other entity.
-
D.
placeRegion
Indicates that a place is located within, or is part of, a larger geographic or administrative region.
-
E.
latitudeRegion
Indicates that an entity is located within, or associated with, a specific geographic region defined by latitude coordinates.
- 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_69e0b4b3a6e08190ae663701f50fab8e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a069edf88190835a9c392c990c55 |
completed | April 20, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:37 a.m.