Triple
T14096991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ernst Schacht |
E339277
|
entity |
| Predicate | materialSpecialization |
P112812
|
FINISHED |
| Object | amber |
—
|
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: amber | Statement: [Ernst Schacht, materialSpecialization, amber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialSpecialization Context triple: [Ernst Schacht, materialSpecialization, amber]
-
A.
materialOptions
Indicates that there are one or more possible materials that can be chosen or applied in relation to a given entity or context.
-
B.
materialCompatibility
Indicates that two or more materials are suitable to be used together without causing adverse interactions, degradation, or performance issues.
-
C.
materialConcept
Indicates that one entity represents or refers to a material-related concept associated with another entity.
-
D.
material
Indicates that one entity is physically composed of, made from, or constructed using the substance or material represented by the other entity.
-
E.
materialParameter
Indicates a relationship where a specific parameter or property is associated with, or characterizes, a material in a given context.
- F. None of above. chosen
Provenance (4 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5fb926288190a7f0f50d1d585d76 |
completed | April 14, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:22 p.m.