Triple
T6287346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAO 94027 |
E140931
|
entity |
| Predicate | isMemberOfHyadesCluster |
P33200
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [SAO 94027, isMemberOfHyadesCluster, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMemberOfHyadesCluster Context triple: [SAO 94027, isMemberOfHyadesCluster, false]
-
A.
belongsToStarCluster
chosen
Indicates that an astronomical object is a member of, or gravitationally bound to, a specific star cluster.
-
B.
hasEmbeddedStarCluster
Indicates that one astronomical object contains or includes a star cluster within its structure or boundaries.
-
C.
cataloguedAsOpenCluster
Indicates that an astronomical object has been classified in a catalog as an open star cluster.
-
D.
isGravitationallyBound
Indicates that one object is held in a stable or semi-stable configuration by the gravitational attraction of another (or others), such that it cannot escape without additional energy.
-
E.
isNearestProminentClusterMemberOf
Indicates that an entity is the closest significant member within a cluster relative to another specified entity or reference point.
- 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.