Triple
T4617746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open cluster M11 |
E100906
|
entity |
| Predicate | trumplerClassification |
P56972
|
FINISHED |
| Object | I,2,r |
—
|
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: I,2,r | Statement: [Open cluster M11, trumplerClassification, I,2,r]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trumplerClassification Context triple: [Open cluster M11, trumplerClassification, I,2,r]
-
A.
spectralClass
Indicates the classification of an astronomical object based on the characteristics of its spectrum, such as temperature and spectral features.
-
B.
dominantSpectralType
Indicates the primary or most prevalent spectral type characterizing the electromagnetic emission of an object or region.
-
C.
luminosityClass
Indicates the stellar luminosity classification that specifies a star’s intrinsic brightness and evolutionary stage.
-
D.
stellarClass
Indicates the spectral classification relationship between a star and its stellar class (e.g., O, B, A, F, G, K, M).
-
E.
spectralTypeOfCompanion
Indicates the spectral classification assigned to a companion object in a system, describing the type of its electromagnetic spectrum.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e098c08190b769e76937dff700 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd556b93cc8190ab817d2817109a0b |
completed | March 20, 2026, 2:10 p.m. |
Created at: March 20, 2026, 1:12 p.m.