Triple
T34233172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 7172 |
E878259
|
entity |
| Predicate | hasObscuredNucleus |
P22860
|
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 7172, hasObscuredNucleus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObscuredNucleus Context triple: [NGC 7172, hasObscuredNucleus, true]
-
A.
isNucleusOf
Indicates that one entity functions as the central or most important core component of another entity.
-
B.
hasNucleusActivity
Indicates that an entity performs, exhibits, or is involved in functional activity occurring within a nucleus.
-
C.
obscuredIn
chosen
Indicates that one entity is hidden, blocked, or made less visible due to the presence or influence of another entity.
-
D.
hasLINERNucleus
Indicates that an entity (typically a galaxy) possesses a nucleus whose emission-line spectrum is characteristic of a Low-Ionization Nuclear Emission-line Region (LINER).
-
E.
hasActiveNucleus
Indicates that the referenced entity possesses a nucleus that is currently functioning or exhibiting biological activity.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f710b339f88190bacc93d09fe8db59 |
completed | May 3, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:56 a.m.