Triple
T20662882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alvan Clark |
E507800
|
entity |
| Predicate | instrumentSpecialty |
P140965
|
FINISHED |
| Object | achromatic refractor objectives |
—
|
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: achromatic refractor objectives | Statement: [Alvan Clark, instrumentSpecialty, achromatic refractor objectives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: instrumentSpecialty Context triple: [Alvan Clark, instrumentSpecialty, achromatic refractor objectives]
-
A.
musicInstrumentation
Indicates the specific instruments or instrumental forces used to perform a piece of music.
-
B.
instrument
Indicates that an action is carried out using a particular tool, means, or implement as its instrument.
-
C.
studiedByInstrument
Indicates that something is examined, measured, or analyzed through the use of a specific instrument or device.
-
D.
notableInstrumentTechnique
Indicates that an entity is particularly recognized for using, developing, or being associated with a specific musical instrument technique.
-
E.
instruments
Indicates that an agent uses a tool, device, or means to carry out an action or achieve an effect.
- 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_69e0b4c059bc81908ea762cd73ea4424 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b2f4872481908858eb88ce89dd47 |
completed | April 20, 2026, 11:12 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 11:44 a.m.