Triple
T20479960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UK Schmidt Telescope |
E502424
|
entity |
| Predicate | correctorPlateDiameter |
P140264
|
FINISHED |
| Object | 1.83 metres |
—
|
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: 1.83 metres | Statement: [UK Schmidt Telescope, correctorPlateDiameter, 1.83 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correctorPlateDiameter Context triple: [UK Schmidt Telescope, correctorPlateDiameter, 1.83 metres]
-
A.
shellDiameter
Indicates the diameter measurement of a shell, typically specifying the distance across it at its widest point.
-
B.
bodyDiameter
Indicates the measurement of how wide an object's body is across its broadest cross-section.
-
C.
trackDiameter
Indicates the diameter measurement of a track, typically specifying the width across its circular or rounded layout.
-
D.
impactorDiameter
Indicates the size of the object that impacts another body, typically measured as the diameter of the impacting body.
-
E.
driverDiameter
Indicates the size of the circular cross-section of a driver component, typically measured as the distance across its widest point.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e58d766b408190a1d3698145fb6d30 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:34 a.m.