Triple
T20479965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UK Schmidt Telescope |
E502424
|
entity |
| Predicate | originalDetectorType |
P7243
|
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: [UK Schmidt Telescope, originalDetectorType, photographic plates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalDetectorType Context triple: [UK Schmidt Telescope, originalDetectorType, photographic plates]
-
A.
primaryDetectorType
Indicates the main kind or category of detector that is used as the primary sensing or measurement component in a given context.
-
B.
detectorType
chosen
Indicates the specific kind or category of detector associated with an entity or measurement.
-
C.
mainDetector
Indicates that an entity serves as the primary or principal detector in relation to another entity or system.
-
D.
detectiveType
Indicates that one entity is classified as a particular type or category of detective in relation to another entity.
-
E.
detectorConfiguration
Indicates a relationship where a detector is associated with, or operates under, a specific configuration or set of parameter settings.
- 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69b55d7a881909dfe3ea0e74b742b |
completed | April 20, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e5768372988190b08ef8ae67d42ab6 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:34 a.m.