Triple
T22695600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Si(Li) detector |
E561163
|
entity |
| Predicate | hasNoiseSource |
P145283
|
FINISHED |
| Object | leakage current |
—
|
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: leakage current | Statement: [Si(Li) detector, hasNoiseSource, leakage current]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoiseSource Context triple: [Si(Li) detector, hasNoiseSource, leakage current]
-
A.
hasNoiseGenerator
chosen
Indicates that an entity is equipped with or associated with a device or mechanism that produces noise.
-
B.
hasNoiseContext
Indicates that an entity is associated with or occurs within a particular noise-related environment or acoustic condition.
-
C.
hasNoiseTerm
Indicates that a given expression, model, or equation includes an additional noise term representing random or unexplained variation.
-
D.
supportsNoiseChannel
Indicates that one entity is capable of handling, transmitting, or operating with a specified noise channel in a system or process.
-
E.
hasNoiseModes
Indicates that an entity supports or is associated with one or more distinct noise-related operating modes or settings.
- 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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789e05d88190b9d51bb3f8e3e9d4 |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:14 p.m.