Triple
T7486488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UVES |
E176893
|
entity |
| Predicate | usesDispersingElement |
P3097
|
FINISHED |
| Object | echelle grating |
—
|
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: echelle grating | Statement: [UVES, usesDispersingElement, echelle grating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDispersingElement Context triple: [UVES, usesDispersingElement, echelle grating]
-
A.
dispersingElement
Indicates that one entity causes another entity to spread out or scatter from a concentrated state into a wider area or among multiple parts.
-
B.
usesElement
chosen
Indicates that one entity makes use of, incorporates, or depends on a specified element in its structure, function, or behavior.
-
C.
usesElementsOf
Indicates that one entity incorporates, applies, or draws upon components, principles, or features derived from another entity.
-
D.
dispersedBy
Indicates that one entity is spread, scattered, or distributed as a result of the actions or influence of another entity.
-
E.
crossDisperser
Indicates that one entity functions as a cross disperser, separating different wavelengths or components of another entity’s output or signal.
- 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_69c69f24ac508190bb98fe927c0bd065 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f5582adc81908b68439762965d88 |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03eeaa88190a5215772ed05ee9f |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:42 p.m.