Triple
T37104985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | η Herculis |
E918816
|
entity |
| Predicate | nearSkyPositionOf |
P38486
|
FINISHED |
| Object | Messier 13 |
—
|
NE NERFINISHED |
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: Messier 13 | Statement: [η Herculis, nearSkyPositionOf, Messier 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearSkyPositionOf Context triple: [η Herculis, nearSkyPositionOf, Messier 13]
-
A.
nearSideOrFarSide
Indicates that one entity is located on either the near side or the far side of another reference point or object, distinguishing relative positional sides.
-
B.
nearCelestialPole
Indicates that one celestial object or point lies close in angular distance to a celestial pole on the sky.
-
C.
ensuredPositionNear
Indicates that one entity caused or guaranteed that another entity was located in close spatial proximity to a specified reference entity or point.
-
D.
nearbyBody
chosen
Indicates that one physical body is located close in space to another body, within a defined proximity threshold.
-
E.
nearestPass
Indicates that one entity is the closest in distance or proximity to another entity compared to all other possible entities or paths.
- 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.