Triple
T18481916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | damped Lyman-alpha system |
E451580
|
entity |
| Predicate | hasObservationTechnique |
P47354
|
FINISHED |
| Object | high-resolution optical and UV 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: high-resolution optical and UV spectroscopy | Statement: [damped Lyman-alpha system, hasObservationTechnique, high-resolution optical and UV spectroscopy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObservationTechnique Context triple: [damped Lyman-alpha system, hasObservationTechnique, high-resolution optical and UV spectroscopy]
-
A.
hasObservationMethod
chosen
Indicates that a particular method, technique, or procedure is used to perform or obtain an observation.
-
B.
hasObservationInstrument
Indicates that a particular instrument or device was used to make or record an observation.
-
C.
observingTechnique
Indicates the method or procedure used to carry out an observation.
-
D.
hasObservation
Indicates that an entity records, contains, or is associated with a specific observation or measured instance.
-
E.
hasTechnique
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e531d3d13c81909c52d797360b840a |
completed | April 19, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:35 a.m.