Triple
T20047217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leo IV Dwarf Galaxy |
E497592
|
entity |
| Predicate | hasHeliocentricDistance_kpc |
P66671
|
FINISHED |
| Object | ~154 |
—
|
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: ~154 | Statement: [Leo IV Dwarf Galaxy, hasHeliocentricDistance_kpc, ~154]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeliocentricDistance_kpc Context triple: [Leo IV Dwarf Galaxy, hasHeliocentricDistance_kpc, ~154]
-
A.
distanceFromGalacticCenter
Indicates the measured or calculated spatial separation between an entity and the center of its galaxy.
-
B.
distanceInMegaparsecs
Indicates the physical separation between two entities measured in units of megaparsecs.
-
C.
distanceToGalacticCenter
Indicates the measured or calculated spatial distance between an entity and the center of its galaxy.
-
D.
hasApproximateDistanceFromEarth
chosen
Indicates that there is an estimated or non-exact distance between an entity and Earth.
-
E.
distanceFromMilkyWay
Indicates the measured or estimated spatial distance between an entity and the Milky Way galaxy.
- 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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6632b2de48190abe2b277d89eb695 |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:37 p.m.