Triple
T19931917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cygnus X complex |
E479073
|
entity |
| Predicate | discoveredAsRadioSource |
P25799
|
FINISHED |
| Object | 1950s |
—
|
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: 1950s | Statement: [Cygnus X complex, discoveredAsRadioSource, 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredAsRadioSource Context triple: [Cygnus X complex, discoveredAsRadioSource, 1950s]
-
A.
discoveredAs
chosen
Indicates that one entity was first identified, found, or recognized in the role or form specified by another entity.
-
B.
isDiscoveredBy
Indicates that something (such as an object, fact, or phenomenon) is found, identified, or revealed by a particular agent or entity.
-
C.
containsRadioSource
Indicates that one entity includes or encompasses a radio source within its spatial or structural extent.
-
D.
primaryBeamSource
Indicates that an entity serves as the originating source of a primary beam used or produced by another entity.
-
E.
discoveredBySpacecraft
Indicates that something was first detected, observed, or found as a result of a spacecraft’s instruments or mission activities.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a14a2348190b41f8e320fe661d6 |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.