Triple
T1416590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coronis (Hyad) |
E31931
|
entity |
| Predicate | clusterType |
P20411
|
FINISHED |
| Object | open cluster member |
—
|
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: open cluster member | Statement: [Coronis (Hyad), clusterType, open cluster member]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clusterType Context triple: [Coronis (Hyad), clusterType, open cluster member]
-
A.
typeOfCluster
chosen
Indicates that one entity is classified as a specific kind or category of cluster in relation to another entity.
-
B.
clusterDensity
Indicates the degree to which elements within a cluster are closely packed or concentrated relative to its size or volume.
-
C.
centerType
Indicates the classification or category of a center (e.g., type of facility, institution, or hub) associated with an entity.
-
D.
competitionCluster
Indicates a relationship where entities are grouped based on participating in or being associated with the same competitive context or rivalry set.
-
E.
regionType
Indicates the classification or category of a region, specifying what kind of region it is (e.g., administrative, geographic, or functional).
- 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c403ccdc8190b2a5fda037b6ea34 |
completed | March 1, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69a4bf060b0081909ba00e6ac093a28b |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.