Triple
T20679806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collinder 140 |
E508259
|
entity |
| Predicate | isNearbyOpenCluster |
P141018
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Collinder 140, isNearbyOpenCluster, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNearbyOpenCluster Context triple: [Collinder 140, isNearbyOpenCluster, true]
-
A.
isOneOfNearestOpenClustersToEarth
Indicates that the subject cluster is among the closest open star clusters to Earth in terms of spatial distance.
-
B.
isOneOfNearestGlobularClusters
Indicates that an entity belongs to the subset of globular clusters that are among the closest in distance to a specified reference point or object.
-
C.
isNearbyGalaxyGroup
Indicates that one galaxy group is located at a relatively close distance to another galaxy group in astronomical terms.
-
D.
isNearbyStarFormingRegion
Indicates that one region of space is a star-forming area located close in distance to another specified reference point or region.
-
E.
hasNearbyMolecularCloud
Indicates that an astronomical object is located close to a molecular cloud in space.
- F. None of above. chosen
Provenance (4 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_69e0b4c1164881909a3bf1e3ddb2bc32 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6bea516b88190b3e90d03fa981a44 |
completed | April 21, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 11:44 a.m.