Triple
T16336048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mössbauer Spectrometer |
E396680
|
entity |
| Predicate | applicationField |
P93839
|
FINISHED |
| Object | mineralogy |
—
|
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: mineralogy | Statement: [Mössbauer Spectrometer, applicationField, mineralogy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applicationField Context triple: [Mössbauer Spectrometer, applicationField, mineralogy]
-
A.
typeOfApplication
Indicates the specific category or kind of application involved in the relationship or action.
-
B.
hasProfessionalApplication
chosen
Indicates that something is used or applied within a professional, occupational, or work-related context.
-
C.
fieldOfWork
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
-
D.
aplicación
Indicates that one entity is the use or implementation of another entity for a specific purpose or function.
-
E.
developedInField
Indicates that an entity (such as a method, theory, or technology) was created, formulated, or advanced within a particular academic or professional field.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4e3af7881908a3116c41ed69115 |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.