Triple
T11109323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simonyi Survey Telescope |
E262713
|
entity |
| Predicate | plannedFirstLight |
P14088
|
FINISHED |
| Object | mid-2020s |
—
|
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: mid-2020s | Statement: [Simonyi Survey Telescope, plannedFirstLight, mid-2020s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedFirstLight Context triple: [Simonyi Survey Telescope, plannedFirstLight, mid-2020s]
-
A.
expectedFirstLight
chosen
Indicates the anticipated time or occurrence of the first appearance of light, such as dawn or initial illumination, in a given context.
-
B.
timeOfRise
Indicates the specific time at which something begins to rise or appear, such as a celestial body or similar phenomenon.
-
C.
firstLightingYear
Indicates the year in which something (such as a light source or lighting installation) was first put into operation or illuminated.
-
D.
plannedAt
Indicates that an event, action, or activity is scheduled or intended to occur at a specific time or date.
-
E.
orbitFirstReachedDate
Indicates the date on which an object first successfully entered and achieved its intended orbit.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a6896c0819082685b5b4600d158 |
completed | April 9, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.