Triple
T17483324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NRZ-L |
E425716
|
entity |
| Predicate | signalShape |
P55008
|
FINISHED |
| Object | rectangular pulses with two 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: rectangular pulses with two levels | Statement: [NRZ-L, signalShape, rectangular pulses with two levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalShape Context triple: [NRZ-L, signalShape, rectangular pulses with two levels]
-
A.
signalType
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
-
B.
inputShape
Indicates the geometric form or configuration that is provided as input to a process, function, or system.
-
C.
shapeType
Indicates the specific geometric form or category that characterizes an entity’s shape.
-
D.
signalTool
Indicates that one entity uses or activates a tool or mechanism to send a signal or convey information to another entity or system.
-
E.
signalProperty
chosen
Indicates that one entity has a specific characteristic, attribute, or feature related to a signal.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451d06c2881909632845dd7a6b1e3 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.