Triple
T37205645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messier 92 |
E922161
|
entity |
| Predicate | nearbyOnSky |
P133149
|
FINISHED |
| Object | north of the star Eta Herculis |
—
|
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: north of the star Eta Herculis | Statement: [Messier 92, nearbyOnSky, north of the star Eta Herculis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyOnSky Context triple: [Messier 92, nearbyOnSky, north of the star Eta Herculis]
-
A.
nearbyObjectOnSky
chosen
Indicates that one object appears close to another object in the sky, as observed from a given viewpoint.
-
B.
nearbyToSolarSystem
Indicates that one astronomical object or region is located at a relatively short distance from the Solar System in space.
-
C.
hasNearbyObservatories
Indicates that one entity has one or more observatories located in close geographic proximity to it.
-
D.
nearbyStarStatus
Indicates whether one celestial object is classified as a nearby star relative to a given reference point or system.
-
E.
nearbyBody
Indicates that one physical body is located close in space to another body, within a defined proximity threshold.
- 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_69f76ea4849481909b4a3073efb0114c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff0b6bc4a88190bf1d38c6ea26bcdc |
completed | May 9, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_69ff082a22f4819095ded971dbd8ea7b |
completed | May 9, 2026, 10:10 a.m. |
Created at: May 3, 2026, 4:15 p.m.