Triple
T15839226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ROSAT |
E384058
|
entity |
| Predicate | performedAllSkySurvey |
P108914
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [ROSAT, performedAllSkySurvey, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedAllSkySurvey Context triple: [ROSAT, performedAllSkySurvey, true]
-
A.
allSkySurveyCompletion
chosen
Indicates that an observational program or mission has finished collecting data over the entire sky.
-
B.
hasDeepSkyObject
Indicates that an entity is associated with or contains a specific deep-sky astronomical object (such as a galaxy, nebula, or star cluster).
-
C.
coSurveyedWith
Indicates that two or more entities participated together in the same survey activity or data-collection effort.
-
D.
hasNoMessierObjects
Indicates that the referenced region or set contains no objects from the Messier catalog.
-
E.
otherGreatObservatories
Indicates a relationship in which an entity is associated with, compared to, or grouped among other major observatories of similarly high importance or capability.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e4fa24819086a1a226082ac2d3 |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.