Triple
T4959164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messier 25 |
E111360
|
entity |
| Predicate | cataloguedAsOpenCluster |
P61439
|
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: [Messier 25, cataloguedAsOpenCluster, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cataloguedAsOpenCluster Context triple: [Messier 25, cataloguedAsOpenCluster, true]
-
A.
isBrightestOpenClusterIn
Indicates that one open star cluster is the most luminous (brightest) among all open clusters within a specified region or context.
-
B.
associatedGlobularCluster
Indicates that one entity is linked or connected to a particular globular cluster in an astronomically relevant way.
-
C.
hasEmbeddedStarCluster
Indicates that one astronomical object contains or includes a star cluster within its structure or boundaries.
-
D.
belongsToStarCluster
Indicates that an astronomical object is a member of, or gravitationally bound to, a specific star cluster.
-
E.
cataloguedAsStar
Indicates that an object has been classified and recorded specifically as a star in a catalog or database.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd72e49b048190bac55d9e7a6f7963 |
completed | March 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69bd71447fe88190bb62c5e8753da7a7 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd72e1b7cc8190b2e621fdf8f22e38 |
completed | March 20, 2026, 4:16 p.m. |
Created at: March 20, 2026, 1:32 p.m.