Triple
T3503584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manchester encoding |
E74022
|
entity |
| Predicate | signalLevel |
P48587
|
FINISHED |
| Object | typically uses two voltage levels |
—
|
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: typically uses two voltage levels | Statement: [Manchester encoding, signalLevel, typically uses two voltage levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalLevel Context triple: [Manchester encoding, signalLevel, typically uses two voltage levels]
-
A.
noiseLevel
Indicates the intensity or amount of sound present in a given environment or from a specific source.
-
B.
signalType
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
-
C.
logicalLevel
Indicates the relative position or depth of something within a hierarchy of abstraction, reasoning, or logical structure.
-
D.
logicLevelDetermines
Indicates that the specific logic level of one entity determines or dictates the resulting state, behavior, or outcome of another entity.
-
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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbf0c2b48190b49923137bb9e45d |
completed | March 8, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69adae0cd8b0819099da300af09880da |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaef1037c819082c7af949ec85360 |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:18 p.m.