Triple
T21294663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 4569 |
E524888
|
entity |
| Predicate | hasCentralStarburst |
P137109
|
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 4569, hasCentralStarburst, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralStarburst Context triple: [NGC 4569, hasCentralStarburst, yes]
-
A.
hasCentralBulge
Indicates that an astronomical object, typically a galaxy, possesses a dense, rounded central concentration of stars or matter.
-
B.
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).
-
C.
hasCentralGalaxy
Indicates that a galaxy cluster or group possesses a specific galaxy that occupies the central, dominant position within it.
-
D.
isStarburstGalaxy
chosen
Indicates that a galaxy exhibits the intense, short-lived burst of star formation characteristic of a starburst galaxy.
-
E.
hasCentralStar
Indicates that an astronomical system or structure possesses a primary star located at its center.
- 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_69e0b517e6748190850d6f6ddf323d69 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73857784881908c3b8418a4c00c1e |
completed | April 21, 2026, 8:41 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:04 p.m.