Triple
T10980698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legacy Survey of Space and Time |
E259495
|
entity |
| Predicate | renamedWith |
P3432
|
FINISHED |
| Object | Vera C. Rubin Observatory naming |
—
|
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: Vera C. Rubin Observatory naming | Statement: [Legacy Survey of Space and Time, renamedWith, Vera C. Rubin Observatory naming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renamedWith Context triple: [Legacy Survey of Space and Time, renamedWith, Vera C. Rubin Observatory naming]
-
A.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
-
B.
renamedTo
chosen
Indicates that an entity has been given a new name, specifying the target name it was changed to.
-
C.
renamedEntity
Indicates that one entity has been given a new name, linking the original entity to its updated or replacement name.
-
D.
renamingAnnouncedBy
Indicates that an entity’s change of name has been publicly announced or made known by another specified entity.
-
E.
replacedWith
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d772e97cf88190a65dab3ec4e5f7f3 |
completed | April 9, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.