Triple
T2968197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Obsidian (color) |
E80216
|
entity |
| Predicate | commonMaterialContext |
P45278
|
FINISHED |
| Object | metal device frames |
—
|
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: metal device frames | Statement: [Obsidian (color), commonMaterialContext, metal device frames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonMaterialContext Context triple: [Obsidian (color), commonMaterialContext, metal device frames]
-
A.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
B.
materialProvidedFor
Indicates that one entity supplies or makes available a material for use, processing, or incorporation by another entity or purpose.
-
C.
canonicalContext
Indicates the standard or primary contextual framework within which an entity, statement, or resource is to be interpreted.
-
D.
contextOf
Indicates that one entity provides the situational, informational, or environmental background within which another entity exists, occurs, or is interpreted.
-
E.
languageOfMaterial
Indicates the language in which a given material, resource, or content is expressed or presented.
- 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_69ad8b14ffe881908ffed62f9595c867 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad996fa4388190abd319c69ee583d9 |
completed | March 8, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69ad960e71f8819088179d11248c6ed0 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad98379fac8190a4dfe530787703c9 |
completed | March 8, 2026, 3:39 p.m. |
Created at: March 8, 2026, 2:58 p.m.