Triple
T364159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble Space Telescope |
E7921
|
entity |
| Predicate | firstLightDate |
P4114
|
FINISHED |
| Object | 1990-05-20 |
—
|
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-05-20 | Statement: [Hubble Space Telescope, firstLightDate, 1990-05-20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLightDate Context triple: [Hubble Space Telescope, firstLightDate, 1990-05-20]
-
A.
firstSuccessfulLaunchDate
Indicates the calendar date on which an entity achieved its first successful launch.
-
B.
firstRaisedAt
Indicates the initial time or context at which an issue, topic, or matter was first brought up or introduced.
-
C.
firstAppeared
chosen
Indicates the earliest known time or context in which an entity was introduced, observed, or came into existence.
-
D.
firstUsedFor
Indicates that one entity was the earliest or original thing for which another entity was used or applied.
-
E.
inceptionDate
Indicates the date on which an entity, event, or relationship was first created, established, or began to exist.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebd1016481909b8ba3b047a47145 |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95dbb208190b277fc5352a4ee84 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.