Triple
T18442726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 3077 |
E450570
|
entity |
| Predicate | hasCentralStarFormingRegion |
P103182
|
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: [NGC 3077, hasCentralStarFormingRegion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralStarFormingRegion Context triple: [NGC 3077, hasCentralStarFormingRegion, true]
-
A.
containsStarFormingRegion
chosen
Indicates that one entity (typically a larger astronomical structure) includes within it a region where new stars are actively forming.
-
B.
hasCentralStar
Indicates that an astronomical system or structure possesses a primary star located at its center.
-
C.
hasStarFormationMode
Indicates the specific manner or process by which star formation occurs in a given astronomical system or region.
-
D.
hasCentralGalaxy
Indicates that a galaxy cluster or group possesses a specific galaxy that occupies the central, dominant position within it.
-
E.
isNonStarformingGalaxy
Indicates that a galaxy does not currently form new stars or has an extremely low rate of star formation.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c11b1288190b9ed4497751197d1 |
completed | April 19, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:30 a.m.