Triple
T4260484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NRZI |
E96090
|
entity |
| Predicate | signalProperty |
P55008
|
FINISHED |
| Object | signal level does not return to a zero baseline between bits |
—
|
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: signal level does not return to a zero baseline between bits | Statement: [NRZI, signalProperty, signal level does not return to a zero baseline between bits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalProperty Context triple: [NRZI, signalProperty, signal level does not return to a zero baseline between bits]
-
A.
signalType
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
-
B.
signalLevel
Indicates the intensity or strength of a transmitted or received signal in a communication context.
-
C.
signalOrigin
Indicates that one entity is the source or starting point from which a signal is generated or transmitted to others.
-
D.
signalVoltage
Indicates the electrical potential level carried by a signal in a circuit or communication channel.
-
E.
signalPolarity
Indicates the directional orientation or sign (positive or negative) of a signal relative to a defined reference.
- 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_69b3454095ac81909c2494f7ff294af1 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34f8103b48190934a810faafa6cb7 |
completed | March 12, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69b347f8dcb08190a725c1f7fb5a7466 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e04ef1c81908bb34ae1cbfab1e6 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:06 p.m.