Triple
T20612999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | openCluster M41 |
E506492
|
entity |
| Predicate | containsStarTypes |
P56969
|
FINISHED |
| Object | red giants |
—
|
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: red giants | Statement: [openCluster M41, containsStarTypes, red giants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsStarTypes Context triple: [openCluster M41, containsStarTypes, red giants]
-
A.
containsStarType
chosen
Indicates that one entity includes or is associated with a star of a specified stellar type.
-
B.
containsAsterism
Indicates that one entity includes or encompasses an asterism (a recognizable pattern or grouping of stars) within its extent or definition.
-
C.
hasStars
Indicates that an entity possesses or is associated with one or more stars.
-
D.
containsStarPositionsFrom
Indicates that one entity includes or is derived from the star position data originating from another entity.
-
E.
containsVariableStars
Indicates that the subject includes one or more stars whose brightness changes over time (variable stars).
- 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aad94dac8190921c7769a649c724 |
completed | April 20, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.