Triple
T3549046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HARPS spectrograph |
E75065
|
entity |
| Predicate | calibrationSource |
P38247
|
FINISHED |
| Object | thorium-argon lamp |
—
|
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: thorium-argon lamp | Statement: [HARPS spectrograph, calibrationSource, thorium-argon lamp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calibrationSource Context triple: [HARPS spectrograph, calibrationSource, thorium-argon lamp]
-
A.
calibratedFor
Indicates that something has been adjusted or tuned to operate accurately or optimally for a specific target, condition, or context.
-
B.
supportsHardwareCalibration
Indicates that one entity provides the capability or functionality to perform calibration operations on another entity’s hardware.
-
C.
commissioningSource
Indicates the origin or authority (such as an institution, program, or body) that formally granted someone their commission or official appointment.
-
D.
measuredFrom
Indicates that a measurement or value is determined relative to, or using, a specified reference point or source.
-
E.
usesSourceType
chosen
Indicates that one entity makes use of, relies on, or operates based on a particular type or category of source.
- 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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbfd278348190ad2fa54f4a423541 |
completed | March 8, 2026, 6:28 p.m. |
| PD | Predicate disambiguation | batch_69adb83270ac819083967db0570167d2 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:20 p.m.