Triple
T23673537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 11-inch Clark refractor |
E584801
|
entity |
| Predicate | opticalQuality |
P52703
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [11-inch Clark refractor, opticalQuality, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opticalQuality Context triple: [11-inch Clark refractor, opticalQuality, high]
-
A.
imageQuality
chosen
Indicates the assessed level or degree of visual clarity, detail, and overall fidelity of an image.
-
B.
opticalSize
Indicates that one entity has a particular visual or perceived size relative to another, often dependent on viewing conditions or context.
-
C.
hasPerceptualQuality
Indicates that something possesses a particular sensory or perceptual characteristic, such as a color, sound, texture, taste, or smell.
-
D.
hasOpticalElement
Indicates that one entity includes, contains, or is equipped with a specific optical element as a component or part.
-
E.
storageQuality
Indicates the degree or standard of how well something is stored, such as its preservation, safety, or suitability for use.
- 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_69e24901421881908c17a5293bdd4a8e |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b410bd788190b2c6853e13287ace |
completed | April 29, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:51 p.m.