Triple
T2375138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vera C. Rubin Observatory |
E46179
|
entity |
| Predicate | dataVolume |
P24102
|
FINISHED |
| Object | tens of terabytes per night |
—
|
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: tens of terabytes per night | Statement: [Vera C. Rubin Observatory, dataVolume, tens of terabytes per night]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataVolume Context triple: [Vera C. Rubin Observatory, dataVolume, tens of terabytes per night]
-
A.
numberOfVolumes
Indicates the total count of separate volumes or parts that make up a multi-volume work or collection.
-
B.
dataStorage
Indicates a relationship where one entity serves as a repository that holds, retains, or maintains data for another entity or process.
-
C.
volume
Indicates the amount of three-dimensional space an entity occupies or contains.
-
D.
storageRequirement
chosen
Indicates the amount or type of storage capacity or resources that an entity needs in order to function or be maintained.
-
E.
dataPortal
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
- 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.