Triple
T24664581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 4696 |
E610635
|
entity |
| Predicate | hasRadioSourceDesignation |
P132325
|
FINISHED |
| Object | PKS 1246-41 |
—
|
NE NERFINISHED |
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: PKS 1246-41 | Statement: [NGC 4696, hasRadioSourceDesignation, PKS 1246-41]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRadioSourceDesignation Context triple: [NGC 4696, hasRadioSourceDesignation, PKS 1246-41]
-
A.
radioSourceDesignation
chosen
Indicates the formal identifier or label assigned to an entity as a radio source in an astronomical catalog or survey.
-
B.
containsRadioSource
Indicates that one entity includes or encompasses a radio source within its spatial or structural extent.
-
C.
hasRadio
Indicates that an entity is equipped with or includes a radio device.
-
D.
hasCallSignOrigin
Indicates that an entity’s call sign originates from, or is derived based on, a particular source, place, or context.
-
E.
hasRadioStation
Indicates that one entity possesses, operates, or is served by a particular radio station.
- 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_69e2c4d505cc8190981881df06c0bf52 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:34 a.m.