Triple
T4637471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schmidt–Cassegrain telescope design |
E101567
|
entity |
| Predicate | correctorLocation |
P47308
|
FINISHED |
| Object | front of telescope tube |
—
|
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: front of telescope tube | Statement: [Schmidt–Cassegrain telescope design, correctorLocation, front of telescope tube]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correctorLocation Context triple: [Schmidt–Cassegrain telescope design, correctorLocation, front of telescope tube]
-
A.
subjectLocation
chosen
Indicates that one entity is located at, in, or near the place or position specified by another entity.
-
B.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
C.
agingLocation
Indicates the place where an entity undergoes an aging process or is stored to age over time.
-
D.
mapLocation
Indicates a relationship where an entity is associated with a specific position or area on a map.
-
E.
leftLocation
Indicates that an entity has departed from or moved away from a specified location.
- 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_69bd43d2f1c081908cd4b7ec48ecc73d |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a62a9e48190b0cf1cbcc51f00c0 |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5233cb5081908807e2b150f0ca06 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.