Triple
T21316278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 4660 |
E525478
|
entity |
| Predicate | AGNActivity |
P133582
|
FINISHED |
| Object | weak or absent |
—
|
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: weak or absent | Statement: [NGC 4660, AGNActivity, weak or absent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AGNActivity Context triple: [NGC 4660, AGNActivity, weak or absent]
-
A.
hasActiveGalacticNucleus
chosen
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.
-
B.
hasAccretionActivity
Indicates that an object is currently undergoing or exhibiting accretion, i.e., the process of accumulating mass from surrounding material.
-
C.
targetedActivity
Indicates that an activity is specifically directed or focused toward a particular entity, group, or objective.
-
D.
associatedActivity
Indicates that one entity is linked to, involved in, or characterized by a particular activity or set of activities.
-
E.
area of activity
Indicates the domain, field, or sphere in which an entity is active or carries out its primary functions or operations.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75dcfdec08190a6e19c907a544921 |
completed | April 21, 2026, 11:21 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:30 p.m.