Triple
T21071277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 4388 |
E519111
|
entity |
| Predicate | hasNuclearObscuration |
P57005
|
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 4388, hasNuclearObscuration, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNuclearObscuration Context triple: [NGC 4388, hasNuclearObscuration, true]
-
A.
hasNuclearPhase
Indicates that an entity undergoes or possesses a distinct stage or period characterized by nuclear-related processes, properties, or activities.
-
B.
hasDustExtinction
chosen
Indicates that an entity exhibits or is subject to attenuation of light due to the presence of intervening dust.
-
C.
hasNuclearRegion
Indicates that an entity possesses or includes a specific nuclear region as a distinct part or component.
-
D.
hasNebulosity
Indicates that one entity possesses or exhibits nebulous, cloud-like, or diffuse characteristics associated with nebulosity.
-
E.
hasActiveGalacticNucleus
Indicates that a galaxy contains an active galactic nucleus, meaning its central region is currently emitting significant energy due to accretion onto a supermassive black hole.
- 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_69e0b505ef108190b25dd4033e2ff7eb |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6feb8ed4481909c9f804ccd8da3e2 |
completed | April 21, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:46 p.m.