Triple
T15637627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schmidt telescope |
E375985
|
entity |
| Predicate | correctorPlatePosition |
P119557
|
FINISHED |
| Object | at or near telescope aperture |
—
|
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: at or near telescope aperture | Statement: [Schmidt telescope, correctorPlatePosition, at or near telescope aperture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correctorPlatePosition Context triple: [Schmidt telescope, correctorPlatePosition, at or near telescope aperture]
-
A.
rackPosition
Indicates the spatial placement or slot of an item within a rack or racking system.
-
B.
classPosition
Indicates the relative ordering or rank of an entity within a class, group, or sequence.
-
C.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
D.
parallelPosition
Indicates that two entities occupy positions that are aligned in parallel relative to a reference frame or axis.
-
E.
ballPlacement
Indicates the spatial positioning or arrangement of a ball relative to a reference point, object, or area.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eba51f08190ac5d9de7fc89405a |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:14 a.m.