Triple
T5683873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andromeda XVII |
E125262
|
entity |
| Predicate | isResolvedIntoStarsBy |
P61266
|
FINISHED |
| Object | large ground-based telescopes |
—
|
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: large ground-based telescopes | Statement: [Andromeda XVII, isResolvedIntoStarsBy, large ground-based telescopes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isResolvedIntoStarsBy Context triple: [Andromeda XVII, isResolvedIntoStarsBy, large ground-based telescopes]
-
A.
isResolvedIntoIndividualStars
chosen
Indicates that an object or region, previously appearing as a single source, can be distinguished into its constituent individual stars.
-
B.
isAsterismOf
Indicates that one or more stars collectively form or belong to a specific asterism.
-
C.
cataloguedAsStar
Indicates that an object has been classified and recorded specifically as a star in a catalog or database.
-
D.
containsStarPositionsFrom
Indicates that one entity includes or is derived from the star position data originating from another entity.
-
E.
belongsToStarCluster
Indicates that an astronomical object is a member of, or gravitationally bound to, a specific star cluster.
- 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_69c0082a884c8190a79001bae658941f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0248751bc8190b12aaa42d1ef17e3 |
completed | March 22, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69c021be59088190a81c880957f666ab |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.