Triple
T20950147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palomar 48-inch Schmidt Telescope |
E515954
|
entity |
| Predicate | originalDetector |
P132777
|
FINISHED |
| Object | photographic plates |
—
|
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: photographic plates | Statement: [Palomar 48-inch Schmidt Telescope, originalDetector, photographic plates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalDetector Context triple: [Palomar 48-inch Schmidt Telescope, originalDetector, photographic plates]
-
A.
mainDetector
Indicates that an entity serves as the primary or principal detector in relation to another entity or system.
-
B.
primaryDetectorType
chosen
Indicates the main kind or category of detector that is used as the primary sensing or measurement component in a given context.
-
C.
detectorType
Indicates the specific kind or category of detector associated with an entity or measurement.
-
D.
usedInDetector
Indicates that something (e.g., a component, material, or method) is employed as part of a detector or detection system.
-
E.
originalFeature
Indicates that one entity is the initial or source feature from which another feature is derived, modified, or referenced.
- 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_69e0b4fcd678819087a304291f14330a |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fadd3bd88190a0d1fdea9d300fc0 |
completed | April 21, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 1:23 p.m.