Triple
T22057883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christmas Tree Cluster |
E545069
|
entity |
| Predicate | isStarFormingRegion |
P146440
|
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: [Christmas Tree Cluster, isStarFormingRegion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStarFormingRegion Context triple: [Christmas Tree Cluster, isStarFormingRegion, true]
-
A.
containsStarFormingRegion
Indicates that one entity (typically a larger astronomical structure) includes within it a region where new stars are actively forming.
-
B.
isStarFormingDwarf
Indicates that the subject is a dwarf galaxy currently undergoing active star formation.
-
C.
isNearbyStarFormingRegion
Indicates that one region of space is a star-forming area located close in distance to another specified reference point or region.
-
D.
isNonStarformingGalaxy
Indicates that a galaxy does not currently form new stars or has an extremely low rate of star formation.
-
E.
hasStarFormationMode
Indicates the specific manner or process by which star formation occurs in a given astronomical system or region.
- 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_69e11e3377c48190890c17407b9527d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1285959f48190b89527b3f9e7ab11 |
completed | April 28, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:27 p.m.