Triple
T19940321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andromeda central supermassive black hole |
E479290
|
entity |
| Predicate | activityClassification |
P8834
|
FINISHED |
| Object | low-luminosity active galactic nucleus |
—
|
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: low-luminosity active galactic nucleus | Statement: [Andromeda central supermassive black hole, activityClassification, low-luminosity active galactic nucleus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activityClassification Context triple: [Andromeda central supermassive black hole, activityClassification, low-luminosity active galactic nucleus]
-
A.
activityType
chosen
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
-
B.
typicalActivity
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
C.
activityStartApprox
Indicates that the start time of an activity is known only approximately, rather than as an exact timestamp.
-
D.
activityTime
Indicates the time period during which an activity occurs or is scheduled to take place.
-
E.
activityLocation
Indicates the place or setting where an activity occurs or is carried out.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a1a8df4819094e84855465df6c0 |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.