Triple
T11583801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supernova Cosmology Project |
E274697
|
entity |
| Predicate | telescopeUsage |
P2518
|
FINISHED |
| Object | ground-based optical telescopes |
—
|
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: ground-based optical telescopes | Statement: [Supernova Cosmology Project, telescopeUsage, ground-based optical telescopes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telescopeUsage Context triple: [Supernova Cosmology Project, telescopeUsage, ground-based optical telescopes]
-
A.
telescopeUsed
Indicates that a particular telescope was employed or utilized to perform an observation or related activity.
-
B.
telescopeType
chosen
Indicates the specific kind or category of telescope associated with an entity.
-
C.
telescopeRole
Indicates the functional role or purpose that a telescope serves within an observation, system, or activity.
-
D.
telescopeConfiguration
Indicates the specific setup or arrangement of components and settings used to operate a telescope.
-
E.
numberOfTelescopes
Indicates the quantity of telescopes associated with a given entity or 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8904db5748190ae5f10ae86ccdf46 |
completed | April 10, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.