Triple
T6088118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timepix pixel detector |
E135689
|
entity |
| Predicate | usesSensorMaterial |
P1272
|
FINISHED |
| Object | silicon |
—
|
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: silicon | Statement: [Timepix pixel detector, usesSensorMaterial, silicon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSensorMaterial Context triple: [Timepix pixel detector, usesSensorMaterial, silicon]
-
A.
materialUsed
chosen
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
B.
appliedToMaterial
Indicates that an action, process, or treatment is performed on or directed toward a specific material.
-
C.
hasMaterialAspect
Indicates that something possesses a physical or tangible component or aspect as part of its overall nature or existence.
-
D.
supportsMaterial
Indicates that one entity provides structural or functional support to a material entity, enabling it to be held, stabilized, or borne.
-
E.
exampleMaterial
Indicates that something serves as a representative or illustrative material or sample of something else.
- 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_69c0087bcc788190b20f093d3a6c60ec |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c057a6f7588190b265d6005fbaf6b3 |
completed | March 22, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69c049f3b1ec8190bea67a7bec6442a5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:12 p.m.