Triple
T6287223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HD 29139 |
E140929
|
entity |
| Predicate | isAsterismPartOf |
P20405
|
FINISHED |
| Object | Hyades region (line-of-sight) |
—
|
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: Hyades region (line-of-sight) | Statement: [HD 29139, isAsterismPartOf, Hyades region (line-of-sight)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAsterismPartOf Context triple: [HD 29139, isAsterismPartOf, Hyades region (line-of-sight)]
-
A.
isAsterismOf
chosen
Indicates that one or more stars collectively form or belong to a specific asterism.
-
B.
partOfConstellation
Indicates that one entity is a component or member star/feature within the larger grouping defined as a specific constellation.
-
C.
containsAsterism
Indicates that one entity includes or encompasses an asterism (a recognizable pattern or grouping of stars) within its extent or definition.
-
D.
positionInAsterism
Indicates the specific location or role that an object occupies within a defined asterism pattern.
-
E.
relatedConstellation
Indicates a relationship where one entity is associated with, connected to, or corresponds to a particular constellation.
- 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_69c008cd17c8819082b82d3fbeb68047 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063ff9f74819088dc603f56fc930c |
completed | March 22, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69c0560a0270819098ad2785b91e8f39 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:26 p.m.