Triple
T2375135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vera C. Rubin Observatory |
E46179
|
entity |
| Predicate | dataProducts |
P3585
|
FINISHED |
| Object | time-domain imaging of the sky |
—
|
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: time-domain imaging of the sky | Statement: [Vera C. Rubin Observatory, dataProducts, time-domain imaging of the sky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataProducts Context triple: [Vera C. Rubin Observatory, dataProducts, time-domain imaging of the sky]
-
A.
productForm
Indicates the specific physical or presentation format in which a product is offered or delivered (e.g., tablet, liquid, package type).
-
B.
productDomain
Indicates the domain, field, or area of application to which a given product belongs or is relevant.
-
C.
productsTraded
Indicates that one entity exchanges or deals specific goods or commodities with another entity.
-
D.
exportProduct
Indicates that an entity sends or sells a product from its own country or region to another country or external market.
-
E.
hasProduct
chosen
Indicates that an entity possesses, offers, or is associated with a particular product.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abca4d89248190be7d712d5fa8382b |
completed | March 7, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69abc59d82f08190b7c36982d1ae783d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:56 p.m.