Triple
T16357554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIFS |
E397220
|
entity |
| Predicate | typeOfSpectroscopy |
P7240
|
FINISHED |
| Object | integral field spectroscopy |
—
|
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: integral field spectroscopy | Statement: [NIFS, typeOfSpectroscopy, integral field spectroscopy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfSpectroscopy Context triple: [NIFS, typeOfSpectroscopy, integral field spectroscopy]
-
A.
spectrometerType
Indicates the specific kind or category of spectrometer associated with or used in relation to an entity.
-
B.
spectrographType
chosen
Indicates the specific kind or category of spectrograph associated with an instrument or observation.
-
C.
hasSpectrograph
Indicates that one entity is equipped with or contains a spectrograph instrument.
-
D.
spectroscopyElement
Indicates that an element is identified or analyzed through a spectroscopy measurement or observation.
-
E.
spectralClass
Indicates the classification of an astronomical object based on the characteristics of its spectrum, such as temperature and spectral features.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2fad0b1948190a66ec7d2a310cc83 |
completed | April 18, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.