Triple
T147055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ritchey–Chrétien reflector |
E3352
|
entity |
| Predicate | typicalMounting |
P2519
|
FINISHED |
| Object | equatorial mount |
—
|
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: equatorial mount | Statement: [Ritchey–Chrétien reflector, typicalMounting, equatorial mount]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMounting Context triple: [Ritchey–Chrétien reflector, typicalMounting, equatorial mount]
-
A.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
-
B.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
C.
mountType
chosen
Indicates the manner or configuration in which one object is mounted or attached to another.
-
D.
typicalUnitSize
Indicates the standard or most common size or quantity in which something is typically measured, packaged, or used.
-
E.
typicalBackground
Indicates that an entity has a usual or commonly expected background, context, or setting associated with it.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256580c2c8190beecca60ca8595f3 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.