Triple
T18442738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 3077 |
E450570
|
entity |
| Predicate | hasStellarShells |
P131614
|
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, hasStellarShells, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStellarShells Context triple: [NGC 3077, hasStellarShells, true]
-
A.
hasStellarWind
Indicates that an astronomical object emits a continuous outflow of gas or charged particles, known as a stellar wind, into the surrounding space.
-
B.
hasStellarStream
Indicates that one astronomical object possesses or is associated with a coherent flow of stars, known as a stellar stream, typically resulting from tidal interactions or disruption.
-
C.
receivesStellarFlux
Indicates that one celestial body is exposed to and absorbs radiant energy emitted by a star.
-
D.
hasStellarSpectrum
Indicates that an astronomical object exhibits a particular stellar spectrum characterizing its emitted light across wavelengths.
-
E.
hasStellarActivity
Indicates that an astronomical object exhibits measurable activity or variability originating from its star, such as flares, spots, or magnetic phenomena.
- 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_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. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:30 a.m.