Triple
T4917279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 224 |
E110378
|
entity |
| Predicate | hasStarFormationRegions |
P22857
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [NGC 224, hasStarFormationRegions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStarFormationRegions Context triple: [NGC 224, hasStarFormationRegions, yes]
-
A.
starFormationActivity
chosen
Indicates the level or intensity of ongoing star formation occurring within an astronomical object or region.
-
B.
starFormationRate
Indicates the rate at which new stars are being formed within a given astronomical region or object over time.
-
C.
isNonStarformingGalaxy
Indicates that a galaxy does not currently form new stars or has an extremely low rate of star formation.
-
D.
containsProminentStarburstGalaxy
Indicates that the subject region or object includes at least one galaxy characterized by a strong, unusually high rate of star formation (a prominent starburst galaxy).
-
E.
hasCentralGalaxy
Indicates that a galaxy cluster or group possesses a specific galaxy that occupies the central, dominant position within it.
- 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_69bd44132b94819088522d92beaadc78 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6fa760448190946401b4b21ea8b7 |
completed | March 20, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.