Triple
T19730066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 5236 |
E473826
|
entity |
| Predicate | isStarburstGalaxy |
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 5236, isStarburstGalaxy, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStarburstGalaxy Context triple: [NGC 5236, isStarburstGalaxy, yes]
-
A.
notableStarburstGalaxy
Indicates that the subject is a starburst galaxy recognized as notable or significant in some context.
-
B.
isDwarfGalaxy
Indicates that the subject galaxy is classified as a dwarf galaxy, typically much smaller and less luminous than standard galaxies.
-
C.
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).
-
D.
isNonStarformingGalaxy
Indicates that a galaxy does not currently form new stars or has an extremely low rate of star formation.
-
E.
isNearestStarburstGalaxyTo
Indicates that one galaxy is the closest starburst galaxy in space relative to another specified object or location.
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e649fbeaf081909e9356229eaf84dd |
completed | April 20, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:47 p.m.