Triple
T1441588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eudora (Hyad) |
E31084
|
entity |
| Predicate | hasClusterType |
P20411
|
FINISHED |
| Object | open star 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 star cluster member | Statement: [Eudora (Hyad), hasClusterType, open star cluster member]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClusterType Context triple: [Eudora (Hyad), hasClusterType, open star 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.
hasITCluster
Indicates that an entity possesses, hosts, or is associated with a specific information technology (IT) cluster.
-
C.
hasCommunityType
Indicates that an entity is associated with or classified under a particular type or category of community.
-
D.
hasMemberType
Indicates that an entity includes or is associated with members belonging to a specified type or category.
-
E.
hasCollectionType
Indicates that an entity is associated with or organized under a specific type or category of collection.
- 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_69a4991633388190a4d61b5a98aa407a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c55714588190a95b4f677c21cbaa |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c47a840c819083307a65c027a19e |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.