Triple
T19686584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scorpius X-1 |
E472725
|
entity |
| Predicate | radioJets |
P136923
|
FINISHED |
| Object | present |
—
|
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: present | Statement: [Scorpius X-1, radioJets, present]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radioJets Context triple: [Scorpius X-1, radioJets, present]
-
A.
radioEmission
Indicates that one entity emits or produces radio-frequency radiation detectable as radio waves.
-
B.
radioEmissionInterpretation
Indicates the inferred meaning, cause, or physical interpretation assigned to an observed radio emission signal.
-
C.
radioSourceDesignation
Indicates the formal identifier or label assigned to an entity as a radio source in an astronomical catalog or survey.
-
D.
associatedRocket
Indicates that one entity is linked or connected to a particular rocket, typically as its counterpart, carrier, or related vehicle.
-
E.
primaryBeamSource
Indicates that an entity serves as the originating source of a primary beam used or produced by another entity.
- F. None of above. chosen
Provenance (4 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6420c3f50819082b64b1fa4335e56 |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:45 p.m.