Triple
T22695592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Si(Li) detector |
E561163
|
entity |
| Predicate | hasSignalReadout |
P149343
|
FINISHED |
| Object | charge-sensitive preamplifier |
—
|
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: charge-sensitive preamplifier | Statement: [Si(Li) detector, hasSignalReadout, charge-sensitive preamplifier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignalReadout Context triple: [Si(Li) detector, hasSignalReadout, charge-sensitive preamplifier]
-
A.
hasReadoutTime
Indicates the duration or timing characteristics required to read out or retrieve data from a device, sensor, or system.
-
B.
hasSignalBox
Indicates that one entity is equipped with, contains, or is associated with a railway signal box used to control train movements.
-
C.
hasSignalLine
Indicates that one entity is connected to another by a signal-carrying line or path used for transmitting information or control signals.
-
D.
readout
Indicates that one entity reports, displays, or outputs the measured or computed value of another entity.
-
E.
hasDigitalSignal
Indicates that an entity possesses, carries, or is associated with a digital (discrete-valued) signal.
- 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_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. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:14 p.m.