Triple
T36293671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble Space Telescope computer |
E893299
|
entity |
| Predicate | firstOperated |
P178233
|
FINISHED |
| Object | 1990 |
—
|
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: 1990 | Statement: [Hubble Space Telescope computer, firstOperated, 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstOperated Context triple: [Hubble Space Telescope computer, firstOperated, 1990]
-
A.
firstOperationalUse
Indicates the point in time or context when something is used operationally for the very first time.
-
B.
initiallyOperated
Indicates that an entity first began functioning, being used, or carrying out its intended operation at a specified initial time or under initial conditions.
-
C.
yearFirstOperational
chosen
Indicates the calendar year in which something first became operational or began functioning in its intended role.
-
D.
operatedSince
Indicates that an entity has been in operation continuously from a specified starting time or date.
-
E.
firstOperationalRole
Indicates the initial functional position, duty, or role an entity first performs or holds in an operational context.
- 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_69f76e4a61f0819084a2b68dbbb4efc6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.