Triple
T32213337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble Space Telescope Treasury programs |
E822863
|
entity |
| Predicate | beganOperationIn |
P3267
|
FINISHED |
| Object | early 2000s |
—
|
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: early 2000s | Statement: [Hubble Space Telescope Treasury programs, beganOperationIn, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganOperationIn Context triple: [Hubble Space Telescope Treasury programs, beganOperationIn, early 2000s]
-
A.
trialOperationsBegan
Indicates that the operational phase of a trial has started.
-
B.
inOperationDuring
Indicates that an entity is actively functioning or in use throughout a specified time period or event.
-
C.
operationStart
chosen
Indicates the point in time or event at which a specific operation or process begins.
-
D.
inOperation
Indicates that an entity (such as a system, device, or facility) is currently active, functioning, and performing its intended operation.
-
E.
enteredIntoOperation
Indicates that an entity has begun functioning or has started its intended operation or activity.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bb94ce188190b3196b0cc902b051 |
completed | May 3, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:37 a.m.